Editing WordPress Optimization

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 174: Line 174:
 
===cPanel Apache Event Configuration===
 
===cPanel Apache Event Configuration===
  
Because cPanel likes to override the main httpd.conf file, which is modified also by WHM global configuration, we will want to put an event ifmodule block in '''pre_virtualhost_global.conf''', this will override any dumb settings '''[[CPanel|cPanel]]''' tries to apply, keeping our event settings at the defaults, which should be fine for most websites. If you are expecting more than 400 concurrent requests then you can raise the "ThreadsPerChild" from 25 to 30, and continue to raise this in small steps until you are happy. Keep in mind that in order to reach this limit '''[[Apache]]''' would need 400 requests AT THE EXACT SAME TIME, it's able to serve lots of requests within a 1 second time span, so if you get 400 requests over the duration of 1 second, these settings would be more than enough to handle the traffic. If anything, PHP is going to be the bottleneck before Apache becomes one.  
+
Because cPanel likes to override the main httpd.conf file, which is modified also by WHM global configuration, we will want to put an event ifmodule block in '''pre_virtualhost_global.conf''', this will override any dumb settings cpanel tries to apply, keeping our event settings at the defaults, which should be fine for most websites. If you are expecting more than 400 concurrent requests then you can raise the "ThreadsPerChild" from 25 to 30, and continue to raise this in small steps until you are happy. Keep in mind that in order to reach this limit Apache would need 400 requests AT THE EXACT SAME TIME, it's able to serve lots of requests within a 1 second time span, so if you get 400 requests over the duration of 1 second, these settings would be more than enough to handle the traffic. If anything, PHP is going to be the bottleneck before Apache becomes one.  
 
<pre>
 
<pre>
 
vim /usr/local/apache/conf/includes/pre_virtualhost_global.conf
 
vim /usr/local/apache/conf/includes/pre_virtualhost_global.conf

Please note that all contributions to wiki.mikejung.biz may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see wiki.mikejung.biz:Copyrights for details). Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)