• susie.Q

    (@susieq-1)


    I have a small blog with only 100-150 visitors/day. When I upgraded to 3.5 in late Dec. I had severe memory problems then and ended reverting back to 3.4.2.

    I have now upgraded to 3.5.1 and the memory problem is even worse.

    I am using the latest version of twenty eleven. I have disabled all of my plugins and nothing changed. Also adding them back one by one also made no difference.

    While I am on a shared server, I am on a large plan and have been extremely happy with my webhost. They have been responsive. They changed the memory value in my php.in file to 384M and the memory in my wp.config file is 125M.

    I may not know very much about computers but that seems like an awful lot of memory. I am currently getting error messages that say:

    Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/mrreeves/public_html/wp-admin/admin-ajax.php, referer: http://mr-reeves.com/wp-admin/post.php?post=7457&action=edit

    Additionally short posts routinely take all 384M and 83 -100% of the mCpu.

    It is not clear what changed with the upgrade to wp3.5.1 that the entry processing and memory demands are so great but I do NOT see this with wp 3.4.2 and they persist even when all the plugins are disabled.

    Since disabling all of the plugins does make a difference and my php.in is already at 384M and by wp-config is set for 125M, I am out of ideas.

    I don’t have the money to upgrade to a virtual cloud acct and for 100 or so visitors, I shouldn’t need to.

    Any any ideas or input is most welcome. Thank you all for your time.

Viewing 2 replies - 1 through 2 (of 2 total)
  • I’m having the exact same issue with my WordPress 3.6 setup. Did you ever find a solution?

    Thread Starter susie.Q

    (@susieq-1)

    Unfortunately, no. It was actually my webhost that increased by my.php to 384M and they also did not see any other issues in the settings on their end.

    The site runs fine and is loads faster than most. The increases are only last for a moment and the webhost hasn’t hassled me over it.

    The problem is still there but is improved when I upgraded to 3.6 and it doesn’t max out the memory or mCpu as often.

    Wish I could be of more help. If it weren’t for security issues, I would run on 3.42 indefinitely.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Severe Memory issue with WP 3.5.1’ is closed to new replies.