From: Harry Edmon <harry@atmos.washington.edu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Network performance degradation from 2.6.11.12 to 2.6.16.20
Date: Sat, 17 Jun 2006 16:23:34 -0700 [thread overview]
Message-ID: <44948EF6.1060201@atmos.washington.edu> (raw)
In-Reply-To: <20060617153511.53a129a3.akpm@osdl.org>
I assume you are talking about using TCP_NODELAY as a socket option within the
LDM software. I could give that a try.
There is a lot of traffic on this node, on the order of 2000 packets in and out
per second, so the tcpdump output will grow pretty fast. How long a tcpdump
would be useful, and what options would you suggest?
I should also note that my network interfaces are Intel, using the latest e1000
driver.
Andrew Morton wrote:
> On Fri, 16 Jun 2006 09:01:23 -0700
> Harry Edmon <harry@atmos.washington.edu> wrote:
>
>> I have a system with a strange network performance degradation from
>> 2.6.11.12 to most recent kernels including 2.6.16.20 and 2.6.17-rc6.
>> The system is has Dual single core Xeons with hyperthreading on. The
>> application is the LDM system from UCAR/Unidata
>> (http://www.unidata.ucar.edu/software/ldm). This system requests
>> weather data from a variety of systems using RPC calls over a reserved
>> TCP port (388), puts them into a memory mapped queue file, and then
>> sends the data out to a variety of downstream requesting systems, again
>> using RPC calls. When the load is heavy, the 2.6.16.20 kernel falls way
>> behind with the data ingestion. The 2.6.11.12 kernel does not. I have
>> tried an experiment with a 2.6.17-rc6 system where it just does the
>> ingestion, and not the downstream distribution, and it is able to keep
>> up. I would really appreciate any pointers as to where the problem may
>> be and how to diagnose it. I have attached the config files from both
>> kernels and the sysctl.conf file I am using. I have also included the
>> output from "netstat -s" on the 2.6.16.20 system during a time when it
>> was having problems.
>>
>
> (added netdev)
>
> A quick grep indicates that it isn't using TCP_NODELAY - we've had problems
> with that in the past.
>
> Perhaps a tcpdump of the net traffic will help to determine what's going on.
--
Dr. Harry Edmon E-MAIL: harry@atmos.washington.edu
206-543-0547 harry@u.washington.edu
Dept of Atmospheric Sciences FAX: 206-543-0308
University of Washington, Box 351640, Seattle, WA 98195-1640
next prev parent reply other threads:[~2006-06-17 23:23 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4492D5D3.4000303@atmos.washington.edu>
2006-06-17 22:35 ` Network performance degradation from 2.6.11.12 to 2.6.16.20 Andrew Morton
2006-06-17 23:23 ` Harry Edmon [this message]
2006-06-17 23:56 ` Andrew Morton
2006-06-18 3:16 ` Stephen Hemminger
2006-06-18 23:23 ` Harry Edmon
2006-06-19 13:54 ` Harry Edmon
2006-06-20 2:11 ` Herbert Xu
2006-06-19 14:47 ` Jesper Dangaard Brouer
2006-06-19 15:24 ` Andi Kleen
2006-06-19 17:34 ` Chris Friesen
2006-06-19 20:39 ` Andi Kleen
2006-06-19 18:24 ` Jesper Dangaard Brouer
2006-06-25 21:51 ` Harry Edmon
2006-06-26 4:20 ` Bill Fink
2006-06-25 22:22 ` Willy Tarreau
2006-06-26 5:23 ` Andi Kleen
2006-07-04 11:41 ` Jesper Dangaard Brouer
2006-07-04 11:54 ` Andi Kleen
2006-07-10 10:55 ` Jesper Dangaard Brouer
2006-09-16 12:08 ` Vladimir B. Savkin
2006-09-18 8:35 ` Andi Kleen
2006-09-18 9:03 ` Vladimir B. Savkin
2006-09-18 9:58 ` Andi Kleen
2006-09-18 10:29 ` Vladimir B. Savkin
2006-09-18 11:27 ` Andi Kleen
2006-09-18 15:38 ` Alexey Kuznetsov
2006-09-18 15:54 ` Andi Kleen
2006-09-18 16:28 ` Alexey Kuznetsov
2006-09-18 16:50 ` Andi Kleen
2006-09-18 21:03 ` Alexey Kuznetsov
2006-09-18 21:22 ` David Miller
2006-09-18 21:46 ` Alexey Kuznetsov
2006-09-19 5:55 ` Andi Kleen
2006-09-19 20:31 ` Thomas Graf
2006-09-19 20:43 ` Andi Kleen
2006-09-19 5:52 ` Andi Kleen
2006-09-18 21:18 ` Vladimir B. Savkin
2006-09-18 22:00 ` Alexey Kuznetsov
2006-09-18 21:57 ` David Lang
2006-09-19 19:40 ` David Miller
2006-09-19 19:44 ` Stephen Hemminger
2006-09-18 22:03 ` Vladimir B. Savkin
2006-09-19 19:41 ` David Miller
2006-09-19 19:47 ` David Miller
2006-09-22 15:35 ` Alexey Kuznetsov
2006-09-22 15:43 ` Andi Kleen
2006-09-22 16:51 ` Rick Jones
2007-03-06 13:25 ` Packet timestamps (was: Re: Network performance degradation from 2.6.11.12 to 2.6.16.20) Vladimir B. Savkin
2007-03-06 14:38 ` Eric Dumazet
2007-03-06 14:43 ` Vladimir B. Savkin
2007-03-06 15:16 ` Eric Dumazet
2007-03-06 18:15 ` Vladimir B. Savkin
2006-09-18 21:08 ` Network performance degradation from 2.6.11.12 to 2.6.16.20 Vladimir B. Savkin
2006-09-18 14:09 ` David Miller
2006-09-18 14:29 ` Andi Kleen
2006-09-18 15:19 ` Alan Cox
2006-09-18 15:19 ` Andi Kleen
2006-06-19 16:40 ` Harry Edmon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44948EF6.1060201@atmos.washington.edu \
--to=harry@atmos.washington.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).