Also make sure you aren't suffering database lock contention from Mysql. This
causes very fast context switching on the database server, and is typically
unable to do useful work even though its load avg is not high. "vmstat" is
useful here.
Sean
On Sat, Apr 28, 2001 at 01:55:01PM -0700, Tim M
David Lang wrote:
>
> watch the resonate heartbeat and see if it is getting lost in the network
> traffic (the resonate logs will show missing heartbeat packets). think
> seriously of setting the resonate stuff to run at a higher priority so
> that it doesn't get behind.
>
> depending on how hig
ed by now (mostly having to do with large number of virtual
IP addresses) but the symptoms were the same.
David Lang
On
Sat, 28 Apr 2001, valery wrote:
> Date: Sat, 28 Apr 2001 11:01:19 +0200
> From: valery <[EMAIL PROTECTED]>
> To: linux kernel <[EMAIL PROTECTED]>
> Subje
I have a high volume web site under linux :
kernel is 2.2.17
hardware is 5 bi-PIII 700Mhz / 512Mb, eepro100
all server are diskless (nfs on an netapp filer) except for tmp and swap
dispatch is done by the Resonate product
web server is apache+php (something like 400 processes), database
backend
4 matches
Mail list logo
