I'm using a Linux Kernel 2.6.32-21-generic and Apache 2.2.14-worker+modsec embedded.
I did some adjusts into worker apache options based in my cpu and memory
# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
I didn't do any modification on Linux Kernel... but maybe we have some options there.
So i defined:
Most of my contents are static, but have some dynamics ones (which make apache process bigger). I can handle ~1.500 connections per second and ~150 concurrent connections. I have have a limited env for testing.
I didn't test using modsec in a separate computer as reverse proxy... but i will do that and send some results.
On Wed, May 25, 2011 at 11:42 PM, Breno Silva <email@example.com> wrote:Hi Breno,
> I spent some time tunning my Linux box and got some good results,
> apache+worker remained stable, a little bit slow after the tunning... but
> responding well. Phoenix did some changes on his env but without success.
Can you describe the Linux and Apache tuning you did that you found to
be effective when using gsblookup?