Thank you for the suggestions. Here is an update with a little more detail. I am testing between cherokee and lighttpd with eccelerator. I think I solved the problem by increasing the
net.ipv4.tcp_mem = 4096000 87380000 4194304000 From: net.ipv4.tcp_mem = somenumber somenumber 393,216 <<<--- wow that seems really low!!!!!!! In /etc/sysctl.conf Anyway, I'm not entirely positive as I can't test it under true load, but I think this fixed it. ab -c 1000 -n 10000 answers all queries in less than 153 ms. However if you could provide any other pointers in terms of optimzing the kernal/linux network settings/performance settings that would be greatly appreciated. Here are some things that I'm aware of already: fs.file-max = 131072 in sysctl.conf server.max-fds=8000 (running lighttpd right now but I think it's 4000 with cherokee, not quite sure if cherokee has settings to change it, but will optimize it when I run cherokee) I have stripped the php-cgi. "PHP_FCGI_CHILDREN" => "1000" plenty of memory left and I think it's a reasonable number, I would like to support that many. I do have a couple of questions: How can one view the number of concurrent connections in real time? Has anyone had experience with the LiteSpeed LSAPI server? Was the performance increase significant. Let's say I'm buying 12 servers<http://forums.devshed.com/#>running lighttpd, would it bring that down to 8 in your opinion? Also, do you know if their licensing when it says, 8-CPU etc, is it cool to run it on 8 different computers with 8 CPUS or is it 8 CPU in one box. I just sent a question to contact but thought'd I'd ask. To elaborate on the symptoms of the previous problem which the tcp_mem possibly fixed: Attempts to load both static and dynamic content take an indefinite amount of time. In most cases the server times out. I am using to lighttpd's lighttpd-status to estimate concurrent connections When I refresh the panel, it shows that there are around 100-150 connections and around 150 requests/s in the last 5 seconds, the server starts to fail at around this threshold. My vmstats show that CPU is 98% idle. Attempts to load Blocks written/read is neglible. MySql <http://forums.devshed.com/#> key_buffer set to 2gb and I'm pretty sure it's not mysql. The overwhelming majority of requests do not access mysql. Thanks! On Wed, Jul 29, 2009 at 4:32 AM, Jorge Sarmiento <[email protected]>wrote: > Try raising the PHP_FCI_CHILDREN as Alvaro says, I got an 8Gb quadcore > server running for 2 months with 200 php-fastcgi processes and it runs > wonderful. > > Jorge S. > > On Wed, Jul 29, 2009 at 2:50 AM, Alvaro Lopez Ortega > <[email protected]>wrote: > >> On 28-jul-09, at 23:49, Stefan de Konink wrote: >> > Hello wrote: >> >> I've stripped the php-cgi so now it allegedly takes up 2.4m at >> >> startup >> >> and probably grows. I am loading 1000 php-fastcgi process and at >> >> around >> >> 150 conncurrent connection the server takes 30-infinity seconds to >> >> respond to some requests while allegedly reponding to some requests >> >> just >> >> fine. Anybody have any idea what's goin on behind the scenes. How are >> >> the fastcgi threads allocated. Why isn't the server responding when >> >> there are allegedly more fastcgi then concurrents. >> >> Actually, php-cgi does not use threads. It forks a fixed number of >> processes defined by the PHP_FCGI_CHILDREN environment variable. Those >> are the processes in charge of executing all the FastCGI requests. In >> case all of them were busy, the news request would have to wait until >> one of them finish its current task. >> >> The easiest solution would be to raise the value of PHP_FCGI_CHILDREN >> so more php-cgi processes are fork()ed, and therefore a higher >> concurrency level is available. >> >> By the way, there is no reason to turn off the keep-alive support. I'd >> rather keep it on (with a sort keep-alive time limit if you wish) so >> clients takes advantage of it. The bottleneck is in php-cgi, Cherokee >> will have no problem what so ever handling those keep-alive >> connections efficiently. >> >> -- >> Octality >> http://www.octality.com/ >> >> _______________________________________________ >> Cherokee mailing list >> [email protected] >> http://lists.octality.com/listinfo/cherokee >> > > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > > -- Phone: 240-529-6770 Aim: flysarescary
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
