WordPress.org

Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #34560, comment 44


Ignore:
Timestamp:
11/24/2015 12:44:25 PM (4 years ago)
Author:
pdfernhout
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34560, comment 44

    v2 v3  
    11@senatorman Thanks for taking the time to report an issue. It's not clear to me yet if what you post on is exactly the "same problem". What you outline sounds more like a general slowdown for all pages rather than a slowdown (or whitescreen or server error) only when opening an editor page? Unless you see a slowdown or errors when editing posts with many revisions, the issue you outline sounds like it is probably different than this one. If it is a different issue, you will get better troubleshooting help by posting elsewhere (to help determine if the issue is too many page views for the server capacity, misbehaving plugins, core WordPress, or something else). Or, alternatively, you might get the issue fixed sooner by finding a WordPress consultant to help you troubleshoot it quickly if it is more about configuration issue than a bug in core WordPress (what this particular Trac system is for).
    22
    3 It looks like from your other posts that you site has more than 40,000 products and others might be [https://wordpress.org/support/topic/wp_load_alloptions-killing-website?replies=2 having a similar issue to what you describe]. If there was any broad similarity to this issue, I would expect it could be from a similar sort of inefficiency somewhere where WordPress might load more data than it has to when loading all options. However, conceptually, that is what wp_load_alloptions should be doing -- loading all options. :-) So, the issue you report could result from from some plugin (or even core code) abusing the options system to store more data there than it should (like setting a unique option for every product or post or something). But without detailed troubleshooting done elsewhere, it's not possible to know. So, I'd encourage you (or someone you hire) to collect some more debugging information on what is stored in the options data for your specific site, and if it then indeed looks like a bug in core WordPress, post a separate Trac issue on it as needed -- or otherwise report the issue to the appropriate plugin maintainer.
     3It looks like from your other posts that you site has more than 40,000 products and others might be [https://wordpress.org/support/topic/wp_load_alloptions-killing-website?replies=2 having a similar issue to what you describe]. If there was any broad similarity to this issue, I would expect it could be from a similar sort of inefficiency somewhere where WordPress might load more data than it has to when loading all options. However, conceptually, that is what wp_load_alloptions should be doing -- loading all options. :-) So, the issue you report could result from from some plugin (or even core code) abusing the options system to store more data there than it should (like setting a unique option for every product or post or something). But without detailed troubleshooting done elsewhere, it's not possible to know. So, I'd encourage you (or someone you hire) to collect some more debugging information on what is stored in the options data for your specific site, and if it then indeed looks like a bug in core WordPress, post a separate Trac issue on it (if needed) -- or otherwise report the issue to the appropriate plugin maintainer.
    44
    55Replying to [comment:43 senatorman]: