In 4.5.2, you introduced a new class called Tribe_Meta_Chunker. We are having serious query performance issues with this update on a high traffic site. We’ve had to revert back to 4.5.1 after only 5 minutes live on our site. Here are my questions.<\/p>\n
1) Where is the supposed to be used, and why is it priming a cache on every page load?
\n2) Where is this mentioned in the changelog? The changelog seemed to be innocuous, but this is a significant change that isn’t mentioned anywhere. I do rely on reviewing changelogs before I roll code on to our production site and need to be able to rely on this sort of stuff being in there.<\/p>\n
The query that is running on each page load is this:<\/p>\n
SELECT post_id, meta_key
\nFROM wp_postmeta
\nWHERE meta_key LIKE ‘_tribe_chunker_%’
\nAND meta_key NOT LIKE ‘_tribe_chunker_%_chunk’<\/p>\n
Our database returns 0 records for this query, yet it takes 0.4 – 1.0 sec to return an answer for a poorly-written MySQL query on a larger database like ours. (we have about 1.5M rows in our postmeta table) Our database is a dedicated box and is not typically under any measurable load until I activate this update.<\/p>\n","protected":false},"template":"","class_list":["post-1288679","topic","type-topic","status-closed","hentry"],"yoast_head":"\n