Recently we noticed that Jetpack Sync is generating a really long query which is killing our DB.
KILLED QUERY (24562 characters long generated in wp-content/plugins/jetpack/sync/class.jetpack-sync-queue.php:372): SELECT option_name AS id, option_value AS value FROM wp_options WHERE option_name IN (‘jpsq_full_sync-1472647887.501315-31118-299-54’, ‘jpsq_full_sync-1472647887.501315-31118-299-55’, ‘jpsq_full_sync-1472647887.501315-31118-299-56’, ‘jpsq_full_sync-1472647887.501315-31118-299-57’, ‘jpsq_full_sync-1472647887.501315-31118-299-58’, ‘jpsq_full_sync-1472647887.501315-31118-299-59’, ‘jpsq_full_sync-1472647887.501315-31118-299-6’, ‘jpsq_full_sync-1472647887.501315-31118-299-60’, ‘jpsq_fu….
When we searched our wp_options table it appeared that we have about 23k entries like that. When I took a look at the option_value for some of these entries, they were referring to posts from 2013. Shouldn’t you remove the old sync entries from the options table?
Can I improve performance of this functionality in any way? I know that there is a setting for the number of rows it will fetch on each call but couldn’t find that in the admin panel.
Also, I’m not sure if we are even using this feature (we are using only Jetpack Json API). Can you explain what exactly it does?
- The topic ‘Jetpack Sync killing the DB’ is closed to new replies.