Changes between Initial Version and Version 1 of Ticket #55206, comment 1
- Timestamp:
- 02/20/2022 02:00:54 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #55206, comment 1
initial v1 3 3 At a glance, the `SAVEQUERIES` constant works as intended here, it is only meant for debugging and not meant to be enabled during large batch processing jobs. 4 4 5 As for the object cache growing, you may get better results using the `wp_suspend_cache_addition()` function introduced in [18681] / #5389 exactly for cases like this. 5 As for the object cache growing, you may get better results using the `wp_suspend_cache_addition()` function introduced in [18681] / #5389 exactly for cases like this. There is also `wp_suspend_cache_invalidation()` introduced in [9106] that might be helpful. 6 6 7 7 So I would say that both `$wpdb` and the object cache work as expected in these circumstances. To impove perfomance of large batch processing jobs, I would suggest looking into asynchronous solutions like [https://github.com/deliciousbrains/wp-background-processing WP Background Processing]. That said, I'm curious to know if you or anyone else have any ideas on how WordPress core could be improved here.