SUMMARY: Recommended /etc/system values for busy webserver?

Thanks to 

Yura Pismerov 
Andrew J Caines

and a few more people whose emails I probably deleted. 

The consensus seemed to be to remove the values from /etc/system that I
migrated over from a similar server, and then to just go into production
with the defaults, with the exception of 

set noexec_user_stack = 1
set noexec_user_stack_log = 1

for security purposes, and

set hme:hme_adv_autoneg_cap=0
set hme:hme_adv_100T4_cap=0 
set hme:hme_adv_100fdx_cap=1 
set hme:hme_adv_100hdx_cap=0 
set hme:hme_adv_10fdx_cap=0 
set hme:hme_adv_10hdx_cap=0

to force 100 mbit full duplex ethernet

On Andrew Caines' suggestion I've installed orca to collect performance
data so I can make an intelligent decision if I see a performance problem,
instead of blindly changing /etc/system values because the "kernel tuning
folklore" says so. Adrian Cockroft says about the same thing in his
performance tuning book, don't believe in /etc/system folklore. It's not
to say that you can't reap performance gains from kernel tuning, you
should just have a good documented reason why you make each change.


Dave Lowenstein
Programmer/Analyst
Instructional Technology Services
San Diego State University
(619)594-0270
http://www-rohan.sdsu.edu/dept/its
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers