Plugin deactivation

So you're getting this problem after wpDiscuz deactivation?

Posted by: Martin Polak

  So you're getting this problem after wpDiscuz deactivation?

Yes

Ok, here you can see the advantage of wpDiscuz plugin. The loading time doesn't have any relation to wpDiscuz if it deactivated. So don't search problems in wpDiscuz. it's deactivated, it's not connected to your website, it can't case any issue.

Here is the real explanation why the native WordPress comment system takes lots of time to load if you have dozens, hundreds and thousands of comments:

For Native WP comment system and for most of all native comment plugins it doesn’t matter how many comments you’ve set to display per post, it loads all comments for that post. Because those use the same “get comments / list comments” function.
Native WP and other native comment plugins load all comments in MySQL buffer even if you set to display one comment on front-end (paginated). So if you have 10,000 comments for one post, and you display 10 comments on first load, WP Native comment system will use the resources for 10,000 comments (mysql time and memory) about 0.1 sec and lots of memory.

wpDiscuz 3 doesn’t use this logic, it doesn't get all comments from database. It builds comment threads using very light SQL queries only for displayed comments, it becomes hundreds of time faster if you have hundreds comments for one post.

Nobody set 1000 or even 10,000 comments at once. In most of cases it’s 50-100. So wpDiscuz will always save your server resources. But the native WP and other native comment plugins will always operate 1000 or 10,000 comments in database and in comment filter functions.

Posted by: Tom

  Ok, here you can see the advantage of wpDiscuz plugin. The loading time doesn't have any relation to wpDiscuz if it deactivated. So don't search problems in wpDiscuz. it's deactivated, it's not connected to your website, it can't case any issue. Here is the real explanation why the native WordPress comment system takes lots of time to load if you have dozens, hundreds and thousands of comments: For Native WP comment system and for most of all native comment plugins it doesn’t matter how many comments you’ve set to display per post, it loads all comments for that post. Because those use the same “get comments / list comments” function. Native WP and other native comment plugins load all comments in MySQL buffer even if you set to display one comment on front-end (paginated). So if you have 10,000 comments for one post, and you display 10 comments on first load, WP Native comment system will use the resources for 10,000 comments (mysql time and memory) about 0.1 sec and lots of memory. wpDiscuz 3 doesn’t use this logic, it doesn't get all comments from database. It builds comment threads using very light SQL queries only for displayed comments, it becomes hundreds of time faster if you have hundreds comments for one post. Nobody set 1000 or even 10,000 comments at once. In most of cases it’s 50-100. So wpDiscuz will always save your server resources. But the native WP and other native comment plugins will always operate 1000 or 10,000 comments in database and in comment filter functions.

In fact, we are using your plugin like an article system so we have more than 9000 comments and we don't use articles so it is maybe the reason.

However, when I'm activating your plugin, the native one from WP will be deactivated or shall I do anything to deactivate it?

I may use an article system in addition of the comment one but I don't know a good plugin to do this because we don't need images but only a system like we are using atm...

Any suggestion?

Thanks for your help Tom.