Messages in this thread | | | Date | Sat, 01 Oct 2011 15:43:02 -0400 | From | starlight@binnacle ... | Subject | Re: big picture UDP/IP performance question re 2.6.18 -> 2.6.32 |
| |
At 09:11 PM 10/1/2011 +0200, Eric Dumazet wrote: >Le samedi 01 octobre 2011 à 14:16 -0400, starlight@binnacle.cx >a écrit : > >2.6.32 has a perf tool, that can really help to >spot in a few minutes hot spots. That would >definitely help to further diagnose what could be >the problem in your workload.
Ok.
First I'm really interested in turning off all the container stuff, so I'm building a 2.6.32.27 kernel that way to see the effect.
If that doesn't fix it, I'll dig in with 'perf' in the RHEL-like build I've tried and found performs the same as RH.
If it does fix it, I doubt much can be done except compile kernels without it.
Haven't been paying attention to containers but now that I've read up on them, it sure sounds like the kind of feature that can double the length of an efficient code-path. Sometimes performance is traded for new features and that's just the way it is. As long as some way to maintain efficiency by shedding them is available, I'll be happy. Our workload is essentially a HPC one, and like most in the HPC realm, we need to be as close to the metal as possible.
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |