Hello Kelvin,
I somehow missed your reply.
On Tue, 2010-02-16 at 15:02 -0500, Kelvin Ku wrote:
> > Did it help?
>
> I switched to an 82576 NIC. The kernel igb driver (version 1.3.16-k2) has
> multiqueue enabled by default with 4 rx and 4 tx queues. I'm running with 4096
> rx ring entries enabled
On Mon, Feb 01, 2010 at 07:35:11AM +0200, Gilboa Davara wrote:
> > >
> > > Can you post the output of $ mpstat -P 1 ALL during peak load?
> > >
> >
> > We run "mpstat -P 5 ALL" continuously; is this sufficient resolution? I've
> > attached the mpstat output from the 09:30-10:30 yesterday, which
On Mon, Feb 01, 2010 at 07:35:11AM +0200, Gilboa Davara wrote:
> On Fri, 2010-01-29 at 14:59 -0500, Kelvin Ku wrote:
> > On Fri, Jan 29, 2010 at 12:22:05PM +0200, Gilboa Davara wrote:
> > > > which
> > > > was throttling the CPUs to 1.6 GHz (from a maximum of 2.4 GHz). I
> > > > attempted to
> > >
On Fri, 2010-01-29 at 14:59 -0500, Kelvin Ku wrote:
> On Fri, Jan 29, 2010 at 12:22:05PM +0200, Gilboa Davara wrote:
> > > which
> > > was throttling the CPUs to 1.6 GHz (from a maximum of 2.4 GHz). I
> > > attempted to
> > > remedy this by setting InterruptThrottleRate=0,0 in the e1000e driver,
On Wed, 2010-01-27 at 10:49 -0500, Kelvin Ku wrote:
> >
> > Please post the output of:
> > $ cat /proc/interrupts | grep eth
>
> We rename our interfaces to lan:
>
> $ grep lan /proc/interrupts
> 61: 1 0 0 0 PCI-MSI-edge lan0
> 62:7194004
Kelvin Ku wrote:
> My question is this: has anyone experienced performance degradation running a
> UDP-consuming application after moving to a Nehalem-based system? We have yet
> to identify whether the culprit is the hardware, the OS, or the combination of
> the two. However, note that our app wor
On Wed, Jan 27, 2010 at 09:01:53AM +0200, Gilboa Davara wrote:
> On Tue, 2010-01-26 at 19:07 -0500, Kelvin Ku wrote:
> > We recently purchased our first Nehalem-based system with a single Xeon
> > E5530
> > CPU. We were unable to boot FC6 on it and are trying to upgrade our network
> > to
> > F11
On Tue, 2010-01-26 at 19:07 -0500, Kelvin Ku wrote:
> We recently purchased our first Nehalem-based system with a single Xeon E5530
> CPU. We were unable to boot FC6 on it and are trying to upgrade our network to
> F11/F12 anyway, so we installed F11 on it.
>
> Our existing hardware includes Xeon
We recently purchased our first Nehalem-based system with a single Xeon E5530
CPU. We were unable to boot FC6 on it and are trying to upgrade our network to
F11/F12 anyway, so we installed F11 on it.
Our existing hardware includes Xeon 5100- and 5400-series CPUs running mainly
FC6 (2.6.22), except
