Linux 2.4 Kernel Tunings used in SPECweb99 results File System Tunings http://www.linuxhq.com/kernel/v2.4/doc/sysctl/fs.txt.html /proc/sys/fs/file-max Maximum number of file-handles that the Linux kernel allocates, hence this establishes the maximum number of files that the system can have open at one time. Default: 4096 Benchmark setting: 100000 IPv4 Tunings URL: http://www.linuxhq.com/kernel/v2.4/doc/networking/ip-sysctl.txt.html /proc/sys/net/core/rmem_max /proc/sys/net/core/rmem_default Default and maximum size of the Linux socket input queues. Larger queue sizes can lead to a reduced risk of delays, so long as one does have the extra memory for the increased queues readily available. Not all combinations of (older) kernels and (older) cards can properly handle larger queue sizes. Default: 65536 Benchmark setting: 1048576 /proc/sys/net/core/wmem_max /proc/sys/net/core/wmem_default Default and maximum size of the Linux socket output queues; this enables web servers to send more of a web page to the network stack in fewer system calls (ideally the entire web page in one call). Default: 65536 Benchmark setting: 1048576 /proc/sys/net/ipv4/ip_local_port_range Set the range of ports that can be used. [Note these values are subject to limitations within the 16bit field that IPv4 uses.] Ports can be used up by network connections in various connected and tear-down states. If/When no more ports are available, any attempt to open a new connect() will fail. Default: 32768 61000 Benchmark setting: 16384 65536 /proc/sys/net/ipv4/ip_forward Do we, or do we not, forward packets between different network interfaces on this system. Default: 0 Benchmark setting: 0 {we will not be forward any packets} /proc/sys/net/ipv4/tcp_sack Do we, or do we not, use the optional TCP selective acknowledgements. [Most useful on lossy, congested, long-delay, or other erratic networks] Default: 1 Benchmark setting: 0 {do not use selective acknowledgements} /proc/sys/net/ipv4/tcp_timestamps Do we, or do we not, use the RFC1323 TCP timestamps. [Most useful on lossy, congested, long-delay, or other erratic networks] Default: 1 Benchmark setting: 0 {do not generate timestamps} /proc/sys/net/ipv4/tcp_window_scaling Do we, or do we not, use the RFC1323 TCP window scaling. [Most useful on lossy, congested, long-delay, or other erratic networks] Default: 1 Benchmark setting: 0 {do not use selective acknowledgements} /proc/sys/net/ipv4/tcp_max_tw_buckets Maximal number of timewait sockets held by system simultaneously. [Web servers with very high hit rates can generate very large numbers of connections in the TIME_WAIT state, and SPECweb99 rules require the web servers to maintain this state for at least 60 seconds.] Benchmark setting: 2000000 /proc/sys/net/ipv4/conf/all/rp_filter - BOOLEAN Do we, or do we not, do source validation by reversed path, as specified in RFC1812. Recommended option for single homed hosts and stub network routers. Default: 0 {No source validation} Benchmark setting: 1 {Drop packets not reachable by this interface} ============================================================================ Chromium X15 WebServer 1.0 Settings used in SPECweb99 results: Module mmap_static Enable module that caches static content. Cache Enable cache for mmap_static module. Default: Off {module not enabled by default" Benchmark setting: On MaxKeepAliveRequests The MaxKeepAliveRequests directive limits the number of requests allowed per connection when KeepAlive is on. If it is set to "0", unlimited requests will be allowed. Default: 100 Benchmark setting: 0 MaxClients The MaxClients directive sets the limit on the number of child processes that will be created to serve requests. Default: 8 Benchmark setting: 1050 SingleListen Web server's socket is bound to specific IP address, not IN_ADDR_ANY. Default: Off {listen to any request however it reached this server} Benchmark setting: On