On Thu, 2002-09-26 at 18:43, Ariel Biener wrote: > > The overview I gave was to explain a pattern of behaviour we have with > really stressed servers here. The service I experienced problem with is > different, and since it's part of a non-disclosure agreement we have, I > cannot specify more. What I can say it that it's a system running an > application which has to be able to deal with ~100Mbit/s full duplex (50 > in 50 out). The system also does ALOT of IO, the system is dual CPU, runs > a database that works pretty hard, and runs 1GB of memory that are ~80% > used.
What device is used for networking? 100Mbit/s on most regular NICs and drivers will kill the system because of interrupt livelock. You *might* benefit alot from using the NAPI network drivers patches, if applicable, which will go to 'polling mode' instead of 'interrupt mode' over specific traffic loads to avoid overloading the system (but still continue to pump packets in and out). I have no idea if this has something to do with the situation your experiencing, but if you do see a really huge numbers of interrupts (/proc/interrupts) during high network loads this might be a good idea in any case and will decrease the load of the system. Gilad. -- Gilad Ben-Yossef <[EMAIL PROTECTED]> http://benyossef.com "Geeks rock bands cool name #8192: RAID against the machine" ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
