Title: Large Memory Usage and Internal Server Errors
Last modified: August 20, 2016

---

# Large Memory Usage and Internal Server Errors

 *  [Wwessex](https://wordpress.org/support/users/wwinter86/)
 * (@wwinter86)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/large-memory-usage-and-internal-server-errors/)
 * Hi,
    When I have W3 Total Cache On the memory usage then doubles, I get a lot
   of out of memory errors and internal server errors. This does not happen with
   the plugin disabled.

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Contributor [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * (@fredericktownes)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/large-memory-usage-and-internal-server-errors/#post-2192571)
 * That’s expected with the current releases (but not future ones), can you increase
   the PHP memory limit using the .htaccess file?
 *  [styzer](https://wordpress.org/support/users/styzer/)
 * (@styzer)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/large-memory-usage-and-internal-server-errors/#post-2192586)
 * Hi Frederick,
 * I too have issues, and our host (BlueHost) is throttling us heavy. W3TC has added
   a whole lot of content to my htaccess file. What should I add to increase memory,
   and where would I insert it (any tags involved?).
 * Many thanks,
 * styzer
 *  Plugin Contributor [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * (@fredericktownes)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/large-memory-usage-and-internal-server-errors/#post-2192601)
 * You didn’t paste the error so I don’t know the exact memory site you need now,
   but for example you could add the following line to the top of .htaccess:
 * `php_value memory_limit 72M`
 *  [styzer](https://wordpress.org/support/users/styzer/)
 * (@styzer)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/large-memory-usage-and-internal-server-errors/#post-2192602)
 * **BINGO!!!!**
    **`php_value memory_limit 72M` is a key!**
 * Hi Frederick,
 * Thanks for the reply. The errors were simply: _“Analysis Error
    The page returned
   an error: 500 Internal Server Error”
   .
 * I also enabled Rocket in the CloudFlare settings and went through the rest of
   the settings and made some changes I thought were going to be helpful.
 * So when I got your reply here, I immediately applied the solution. But before
   adding the line you gave me I ran a speed test:
    [http://gtmetrix.com/reports/www.iamsignificant.ca/9oJB9R9y](http://gtmetrix.com/reports/www.iamsignificant.ca/9oJB9R9y)
 * I then added the line to my htaccess file and uploaded it to the server. Running
   a new speed test, I got the above Internal Error message.
 * I clicked to run the test again and this time it carried the test through, reporting:
   
   [http://gtmetrix.com/reports/www.iamsignificant.ca/PFHmsf0U](http://gtmetrix.com/reports/www.iamsignificant.ca/PFHmsf0U)
 * **I raised the number to 128M** and tested again, same error message, and then
   again I tried running the test successfully. Results:
    [http://gtmetrix.com/reports/www.iamsignificant.ca/kxNoYOZf](http://gtmetrix.com/reports/www.iamsignificant.ca/kxNoYOZf)
 * **So your solution did something! **
 * When I look at the tests results, I find that before inserting the **72M** code,
   the line “Enable gzip compression” was showing a grade of **F 14**. Now with 
   the **72M** specified, the grade is still at **F 14**. But using **128M** brings
   that line at **A 100**. So I left the value of **128M** since it gives a noticeable
   increase in the test results.
 * Those are the little mysteries regular guys like me are thankful for brains like
   yours who can help us out, it may feel simple for coders, but not being one, 
   I deeply value your help… :O)
 * About CloudFlare: I do hope they will reward you for your contribution and how
   many people you turned their way…
 * Many thanks for everything!
 * Regards,
 * Andre Lefebvre
 *  Thread Starter [Wwessex](https://wordpress.org/support/users/wwinter86/)
 * (@wwinter86)
 * [14 years, 10 months ago](https://wordpress.org/support/topic/large-memory-usage-and-internal-server-errors/#post-2192621)
 * Hi,
    php_value memory_limit 72M does not help me sorry, When I put this at the
   top of my .htaccess file I get a permanent ‘Internal Server Error’ until I remove
   it. My site is [http://www.freefullvideosonline.com](http://www.freefullvideosonline.com)
   Any ideas please?
 *  Plugin Contributor [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * (@fredericktownes)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/large-memory-usage-and-internal-server-errors/#post-2192658)
 * [@styzer](https://wordpress.org/support/users/styzer/), W3TC needs far less memory
   in the latest release. Please upgrade. About cloudflare, please mention that 
   to them if you don’t mind. 🙂
 * [@wwinter86](https://wordpress.org/support/users/wwinter86/), please upgrade 
   to reduce memory usage. As for the 500 error there, ask your host why that doesn’t
   work for you, it’s quite unique.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Large Memory Usage and Internal Server Errors’ is closed to new replies.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [Frederick Townes](https://wordpress.org/support/users/fredericktownes/)
 * Last activity: [14 years, 8 months ago](https://wordpress.org/support/topic/large-memory-usage-and-internal-server-errors/#post-2192658)
 * Status: not resolved