<snip>
taking 8-10 seconds. I understand that our network might be saturated,
but I don't understand why pound is being bottlenecked within code where
no network operations are being performed. This sounds like a
thread-management problem in the kernel. Has anybody heard of this type
of problem?
Under normal conditions (with 100 concurrent requests), the same "for"
loop takes under 0.100 milliseconds -- 30,000 times faster. Is there
anything I should check?
<snip>
I'd tend to agree with your gut feel. Something outside of pound is
changing the time it takes for pound to do the same job! What does
'top' report when you're at peak usage? I'm mostly curious if your CPU
is spending all its time processing interrupts instead of user code.
Any idea how many packets/second you're moving? Also - what are the CPU
/ NIC / bus specs on this machine?
--
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.com/
--
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
