Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 189
  • Last Modified:

WordPress, AWS and memory starvation

I needed to upgrade a little WordPress site to an ExtraLarge partition today since httpd was failing to start due to a memory problem. The suggestion by AWS was to run MySQL on a different instance than WordPress. Meanwhile, I need to pay more for that server.

He also said there could be a memory leak in the code.

What kinds of things could cause a memory leak in the WordPress code?

How confident are you the problem will be solved when I decouple the DB from my Web Server?

Thanks.
0
newbieweb
Asked:
newbieweb
  • 2
  • 2
3 Solutions
 
chilternPCCommented:
if you have a memory leak in your code then moving the and decoupling things is not going to fix that.

Have you checked or set  the memory limit in your wp-config.php file in the root wordpress folder?

look for 'WP_MEMORY_LIMIT' in the wp-config.php file and either increase it to 64M  or add the line inside the main php tag:
 
define('WP_MEMORY_LIMIT', '64M');

If you still get the error after this change, then please contact your AWS. Most likely, they would have to go in their php.ini file to increase the memory limit for you.
1
 
newbiewebSr. Software EngineerAuthor Commented:
A) He suggested a memory leak as a possibility, but is that even possible with WordPress?

B) He suggested the real cause we do not have enough memory is that one server hosts WordPress AND MySQL.

What are the odds it B?
0
 
William NettmannPHP Web DeveloperCommented:
a) WordPress, or a theme or plugin, could conceivably have a memory leak. The generally accepted approach to find the source of a problem in WordPress is to disable all plugins and revert to a default theme, e.g. Twenty Sixteen, check if the error continues (if it does, WordPress, data, config or environment is the problem) and if not, add back each plugin and theme one at a time to see which one causes the issue.

b) Many WordPress installations run the web server and MySQL on the same server - and often, PostFix, Bind, Dovecote and other services as well. It is unlikely that running the web server (WordPress) and MySQL on the same server is a problem as such.

The most probable solution to your problem, all things being equal, is to allocate more memory to your AWS instance, and yes, pay more for it.
1
 
chilternPCCommented:
did you check the  memory limit in your wp-config.php file in the root wordpress folder?
1
 
newbiewebSr. Software EngineerAuthor Commented:
thanks
0

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now