Re: big picture UDP/IP performance question re 2.6.18 -> 2.6.32
Date: Sat Oct 01 2011 - 17:16:25 EST
[resend, accidently pasted HTML that VGER bounced]
At Sat 14:41:06 EST 10/1/2011 -0400, Willy Tarreau wrote:
>Just a suggestion, instead of measuring CPU usage
>at a given load, could you check what maximal load
>you can achieve?
Did do that and mentioned it in one of my replies.
Essentially the same result, see comment below.
>It is very possible that CPU
>usage report is not accurate. We observed this in
>a number of situations, especially in high packet
>rate environments where the usage is a sum of many
Thanks for the suggestion Willy.
I'm completely on top of the CPU accounting
aliasing problem. The playback server sends
data in pulses on one-millisecond boundaries
due to the behavior of nsleep() when used to
pace a log playback. The receiving system
clock drifts at a rate that is about 60 PPM
different than the transmitting server clock
(according to 'ntpd' synced to within 20 micro-
seconds of a local CDMA time server), and so the
histogram accounting on clock tick intervals
gradually drifts such that CPU displayed by 'top'
and 'vmstat' is actually a varying slice of the
millisecond interval pulse profile. Takes
about 60 seconds for the alias sample
window to drift through the entire pulse.
Turns out if one understands the effect it
adds some value to the recorded CPU statistics.
One can see that the kernel CPU peak arrives
immediately and decays while the user CPU
peak follow somewhere between 150 and 250
microseconds after the kernel peak.
Makes perfect sense as at the start of the
pulse the packets are being processed in the
kernel and are then handed off to the application.
Anyway the test run is 20 minutes long so the
values reported here are accurate due to
the averaging-out of the aliasing effect.
As mentioned in one of my posts, do also run
at close to 100% utilization where the
aliasing effect does not distort results.
Outcome is the same as the 50% load runs
except that the code runs 20% more efficiently
at full due to batching of packets with
fewer interrupts and context switches.
>Also, I did not notice any indication on the load
>level you were reaching (packets per second and
20% bandwidth and 50k pps on four links for
half-load test, 200k pps total
40% bandwidth and 100k pps on four links for
full-load test, 400k pps total
>Have you compared the interrupt rate?
>It is possible that they differ between the two
>kernels, for instance because the NIC auto-adapts
>instead of being throttled to a given rate. This
>can have a significant impact on measurements and
The interrupt rates are about the same. Ran
the test with the exact same 'e1000e' driver
compiled from the Intel SourceForge version.
Native 'e1000e' runs something like 0.5%
Willy, Sorry your e-mail was blocked. Forgot
to turn off the non-US country block I use
to limit spam. It's off now and I'll keep
it off for a couple of days.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/