Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Dani Llewellyn

    (@diddledani)

    I would expect you’re hitting an upper-limit due to the size of the list. I’m working on improving the performance and issues with large lists for the future, but I don’t have a solution for you right now :-(.

    Thread Starter elrebrin

    (@elrebrin)

    @diddledan – ah, I see. What’s the current threshold, and is there any workaround? I’d like to keep our Game Page page operational because it’s something that we really need! Game Reviews isn’t essential, but it’s a huge want for sure!

    Plugin Author Dani Llewellyn

    (@diddledani)

    I don’t have an exact figure because it depends on the resources available at your web host. Different sites will hit the problem at different sized lists because of variances in cpu, memory allocation, and overall load for the PHP runtime and the database.

    Thread Starter elrebrin

    (@elrebrin)

    Heh, well we have 28GB RAM Available on our web host w/ plenty of CPU as well ??

    Not shared hosting, 100% self hosted arch/nginx config

    Plugin Author Dani Llewellyn

    (@diddledani)

    If you want to dig-in I’m expecting that PHP died due to resource exhaustion or timeout – you can try finding the error log of your server to see whether my guess is correct which might give you ideas to mitigate it for now such as either increasing the memory limit for PHP or finding out whether it timed out due to mysql responding slowly or just a nature of physics. if mysql is responding slowly you could try adding in a memory cache or attempting to tune mysql or both.

    Thread Starter elrebrin

    (@elrebrin)

    Logs pulled:

    2017/10/24 18:43:47 [error] 11587#11587: *576158 FastCGI sent in stderr: “PHP message: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in %PATHOBSCURED%/wp-includes/meta.php on line 841” while reading response header from upstream, client: MYLOCALWANIP, server: techraptor.net, request: “GET /game-reviews-directory HTTP/1.1”, upstream: “%FASTCGIPATH%/php-fpm/php-fpm.sock:”, host: “techraptor.net”

    Looks like about 134kb memory per title, at an average of 29 characters per title maybe? Just some really rough math.

    Thread Starter elrebrin

    (@elrebrin)

    To make it work, just for shits and giggles – I upped our PHP allowed to 256MB.

    It worked: https://techraptor.net/game-reviews-directory

    Will be dropping that shortly.

    Plugin Author Dani Llewellyn

    (@diddledani)

    OK,

    Sorry about the long delay in replying. I’ve put together an updated version, which might solve this problem for you. It is available at https://github.com/diddledan/wp-a-z-listing/archive/2.0.zip as a pre-release, and includes some caching strategies. When the cache is cold, though, it will still take a lot of memory and time to build the page.

    It looks from your error above that the memory exhaustion occurred in meta.php from WordPress core. That would indicate that perhaps the problem is related to a large amount of metadata on your posts. It would be interesting to see if you could isolate whether the plugin fails on your posts in isolation or whether it is a combination of plugins which is causing the issues.

    For reference, I’ve just tested the 2.0 preview on a local system with a memory limit of 128M and 10,000 posts without hitting the limit.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Blank page for one type, working for another’ is closed to new replies.