12-01-2019, 06:31 AM
(02-04-2019, 05:49 PM)rudra Wrote: there is no best parameter or value for the ones posted above. good values vary from case to case or else the guys would mention these so called best values in comments of the associated settings file. a totally silly thread in my opinion. no explanation nothing. please explain and give source reference. thanks
I would agree with @rudra's assessment of this; Apache web server (httpd) is a mighty mighty beast and the way it has been treated in the OP is (... well) disrespectful to its seniority.
I've worked with this fellow(/httpd) for the last 16 years in various configurations, but (truth to be told) never on high-traffic websites. I've compiled it from source, tweak it in various ways, put the PHP handler on top of it in various mod (DSO, FCGI etc..), used it to reverse proxy Node.js apps running in the background, put Nginx in front of it to serve static files and protect it from DDoSing attacks and still ... I just can't say that I've explored every bit of it.
What's clear is that the OP is talking about Apache's configuration in WHM (I didn't know what that is till I googled it--or I knew but I forgot?; the Web Host Manager.) Well, I'm not familiar with that interface, so I'll just refer folks here who are asking for the meaning of those directives to see here, for example. Although, I would advice consulting HTTPD documentation's web site. For the list/details of all the directives check here.
As a veteran, I only use a text editor and tweak those directives right inside the httpd.conf file (Apache's configuration file) located inside the /conf folder of Apache's main directory.
Then I run a syntax check to see if I didn't introduce any misconfiguration by running:
Code: (Select All)
httpd -t
Then I restart the beast:
Code: (Select All)
httpd -k start
But, really the most key thing to know about Apache Web server is that HTTPD can run in 3 different ways, depending on which MPM module you activate/load in the config file:
> event MPM module
> worker MPM module
> prefork MPM module
The most efficient and recent mode is the event module (uses threads and Async capabilities), while the prefork MPM is the old process-based way (inherited from Apache 1.)
I think, I will stop here, because there is so much details involved in each and every directive you set and every module you chose to load or not.