Notifications
Clear all
Topic starter
04/06/2018 3:40 pm
Dear gVectors Team,
After upgrading the wpDiscuz (free) plugin from 5.0.x to 5.1.x we have noticed that the wp_option table gets filled up with wpdiscuz-related transient entries really quickly on our website that is seeing a ton of traffic every day.
This is causing a rather considerable amount of database performance regression in the negative sense of the word, and causes queries like these to return a lot slower and a lot more data than usually, causing serious problems to us:
SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes';
Is there any way to turn off this new behavior? Or are we forced to roll back to your 5.0.x versions forever?
Example transient entries would include: _transient_wpdiscuz_replies_count_XXXXX, _transient_wpdiscuz_threads_count_XXXXX, _transient_wpdiscuz_authors_count_XXXXX.
Before this upgrade, an average wp_options table contained less than 1.000 rows (usually around 600).
Your plugin manages to put in around 500.000 (!) additional rows filled with these transients. This is obviously a huge amount of data growth, which we found via here: https://wordpress.stackexchange.com/questions/71691/slow-query-for-the-wp-options-table
This page explains why this usually should be avoided: https://kinsta.com/knowledgebase/wp-options-autoloaded-data/
Looking forward to hear from you, the plugin functionality is great but this is a blocking issue right now for us.
04/06/2018 9:34 pm
Hi @djvdorp,
It seems something went wrong, or you have a large amount of posts. wpDiscuz should not put 500.000 additional rows filled with transients. At the moment we're working on this and are developing other ways of caching without transients. All transients will be removed automatically by WordPress very soon. You just need to disable "Discussion Statistics" and "Recent Comment Authors" components in Dashboard > Comments > Settings > Comment Form Tab.
Topic starter
05/06/2018 10:22 am
Hi @Tom,
Thank you for the quick and helpful reply, it is good to know that you are working on this and are developing other ways of caching without transients, as that will perform a lot better most likely and also is a lot cleaner to do actually. We do actually have a large amount of posts -- in the direction of ~75k items in wp_posts with ~16k of them published.
The solution that you posted above (disable "Discussion Statistics" and "Recent Comment Authors" components in Dashboard > Comments > Settings > Comment Form Tab) worked out well enough for the time being, so in that sense this topic can be considered to mark as closed. The only thing I would like to additionally request is that these kind of behavioral changes (eg. caching heavily in transients) are added to this and future changelogs for admins.
05/06/2018 3:15 pm
Hi djvdorp,
This is already fixed, and we are preparing a new wpDiscuz version, please wait for the next update, it comes soon.
22/10/2018 2:00 pm
Guys, this topic was made on June. When can we expect the update? This issue affects my portal while I was really hoping to get a sollution, rather then another problem after solving original problem.
This post was modified 6 years ago by Wojciech Mrozowski
22/10/2018 2:22 pm
Hi @infotakedown-pl,
This issue is solved long time ago. Why not just update and see that?
Topic starter
09/11/2018 10:45 pm
This issue seems still present for us in the latest available version right now (5.2.2), and not present in eg. 5.1.5.