Hi Ryan,
Besides upgrading Zenbu (and EE if possible), — I’m not teaching you anything here ;) —, you might want to consider increasing PHP memory if it’s on the low side, or at least to see if that makes a difference. This is particularly true if you see a message with the CP hang mentioning out-of-memory errors.
Zenbu searches in the 3rd-party Matrix database tables, concatenates its data, and Zenbu searches for a match on this concatenated string. For a large number of data, these queries of course possibly add a lot to the number of things to process by Zenbu. A “performance mode” in Zenbu, where the search is simply done in the exp_channel_data table, is sounding like an interesting feature to add in the future, though! :)
In the meantime, if a memory increase isn’t helping, or you can’t make that change, you could try disabling the method that is doing these extra, Matrix-related queries. In /system/expressionengine/third_party/zenbu/fieldtypes/matrix.php, rename the **zenbu_result_query** method to something else. Anything will do. This will disable this method from being called, and therefore the fieldtype-specific queries, and fall back to searching in exp_channel_data. Of course, make sure your Matrix data is saved in exp_channel_data by making your Matrix columns searchable in the custom field settings.
Lastly, does the site have a lot of authors and/or templates? The upcoming Zenbu 1.9.3 will have improvements on this front, which should help with performance on member/template-heavy sites.
|