WordPress.org

Ready to get started?Download WordPress

Forums

Hitting Host's 500 MB Memory Usage (RAM) Limit (35 posts)

  1. browndog82
    Member
    Posted 3 years ago #

    Man, I just don't know. This is my first time modifying the robots.txt file for a WP site, and I actually haven't done it yet. We better wait for an expert to chime in on this one...

  2. bcgear
    Member
    Posted 3 years ago #

    Waiting too! I'll check back later. I'm going back to my HG support with a few more questions. This is crazy, all these errors. SO far, my site is not getting disabled again by server control personnel, so I guess I'm happy for now.

    THAT was really unpleasant & happened right in the middle of the big event I was marketing for, just when my clicks & traffic started going really really well, the whole thing went down with internal error blah blah. We all learn the 'overloaded server' lesson the hard way, putting off the expensive VPS or dedicated server account upgrade until it we are forced.

    It was not difficult to upgrade, HG did all the work, but I'm disappointed that the same issues are happening PLUS a new error. Heavy Sigh. I'm going outside to remember clear the dust.

  3. ssweeps
    Member
    Posted 3 years ago #

    I am getting the same errors: cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp

    It is on various files.

    My issue started around June 5th. I had about 8 sites on a shared hosting acct with Hostgator for a year and in this one day something happened and my account hit their 25% memory usage and everything ground to a halt.

    As of today all of my sites are on a VPS level 7 with them but the errors persist. I don't think the original problem got taken care of and now I can't figure out what is happening.

    The 2 things I did on that day I removed and they were just graphics that were ads so no new plugins or scripts. I have disable, uninstalled and upgraded plugins on all sites. I installed Total Cache on all and repaired all databases. Still the problem persists.

    Hostgator has spent many hours on the phone with me but they can't figure it out either. They even upgraded the memory allocated for PHP to 2 GB because it was set to 64 MG.

    Can anyone help? How can I go back and figure out what happened on that day to cause the problem? Is there a tool(s) to track down the cause?

    Thanks for your help.

  4. A2JC4life
    Member
    Posted 3 years ago #

    I have had similar issues, as well. I can't seem to narrow it down to one particular plugin or anything. If all plugins are removed, it seems to be okay, but adding them back in eventually hits a threshold the server can't handle. My site is not huge, so I have a hard time imagining that I'm pulling far more resources than normal.

    I wish the WP team would address this. When I asked about it before, I was basically told to just upgrade my hosting, but that seems like more of a band-aid fix than a real solution.

  5. Jolyon
    Member
    Posted 2 years ago #

    I believe I have found the cause of all these issues!
    CloudLinux (excellent idea and product) limits my RAM to 256MB.
    My host has PHP's memory_limit set to 128MB.
    When a PHP page is first called, the memory_limit of 128MB is assigned (for ~100 milliseconds), then reduced to the actual RAM required (in my case, 524KB).
    I'm not using WordPress, but have AJAX code calling multiple PHP pages simultaneously - wham, I hit the limit.
    I have some (relatively) simple demo code, which you are free to copy and use to test with at:
    http://DingoSeatCovers.com.au/demo
    The PHP pages are one-liners.
    I'm trying to persuade my Website Host to reduce PHP's memory_limit from 128MB to reduce this issue.
    Anyone have contacts with Apache/PHP to see if the "assign memory_limit" could be changed?
    Contacted CloudLinux, but no success, as they do not consider it their problem - fair enough, I think.

    Most aggravating thing is, Website Hosts see this as a "we have found the heavy users, and they are the problem". No, the heavy users are more likely to see this issue, but the problem is a very high PHP memory use (very brief, but actual) and CloudLinux seeing that breaching the limit.

    My code (not fancy) did not automatically retry when finding 500 errors, so I saw the exact problem much earlier and more easily.
    Most good code (jQuery and WP) is likely to retry the 500 errors, and so mask this problem from sites with low usage.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.