mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danial Thom <danial_thom@yahoo.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 Performance problems
Date: Sat, 27 Aug 2005 07:44:59 -0700 (PDT)	[thread overview]
Message-ID: <20050827144459.66078.qmail@web33304.mail.mud.yahoo.com> (raw)
In-Reply-To: <430FA544.8000603@candelatech.com>



--- Ben Greear <greearb@candelatech.com> wrote:

> Danial Thom wrote:
> 
> > I didn't refuse. I just chose to take help
> from
> > Ben, because Ben took the time to reproduce
> the
> > problem and to provide useful settings that
> made
> > sense to me. There's nothing wrong with my
> > machine. 
> 
> Well, I didn't see the slowdown on my system
> when I tried 2.6
> v/s 2.4.  You reported a 3x slowdown.  In your
> original mail,
> you didn't mention trying to do compiles at the
> same time
> as your network test.  I *did* see a pathetic
> slowdown (from 250kpps
> bridging to about 6kpps getting through the
> bridge) when I coppied
> a 512MB CDROM to the HD, but let's get the pure
> network slowdown
> on your system figured out before we start
> looking at the impact
> of disk IO.
> 
> So, if you see a 3x slowdown on an unloaded
> machine when going
> from 2.4 to 2.6, then there is something unique
> about your system
> and we should figure out what it is.
> 
> Also, my numbers (about 250kpps with moderate
> amount of drops)
> was a lot better than the 100kpps you reported
> for 2.6.  My
> hardware is different (P-IV, HT, 3.0Ghz 1MB
> Cache, 1GB RAM,
> dual Intel pro/1000 NIC in PCI-X 66/133 slot),
> but I would not
> expect that to be 2x faster than your Opteron
> (or whatever you had).
> 
> You could mention what you are using to
> generate traffic.  (I was
> using pktgen to generate a stream of 60 byte
> pkts.)
> 
> I think you should give us some better
> information on exactly
> what you are doing on 2.4 v/s 2.6.  And for
> heaven's sake,
> don't hesitate to send kernel configs and
> hardware listings
> to folks that ask.  Ruling out problems is as
> useful as finding
> problems in this sort of thing.

Ok, good point, but I think  the original issue
has evolved into "why does linux drop packets
even when its not close to capacity". Its not
really a "slow down" now that we've been
discussing it, its the point at which packet loss
begins to occur. And since it appears that packet
loss can occur at usage levels not even close to
capacity, I can't really determine the capacity.
Since CPU usage also doesn't seem to register
correctly, I can't get a handle on the load for
various activities. So it may not have anything
to do with "slowness". I feel like I'm trying to
weigh a big blob of Jell-o that keeps falling off
the scale. 

The bottom line is that if I can't get it to stop
dropping packets, the performance is moot,
because its simply not suitable for my needs.

DT


		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 

  reply	other threads:[~2005-08-27 14:45 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2230.192.167.206.189.1124721719.squirrel@new.host.name>
2005-08-22 15:41 ` Danial Thom
2005-08-26 13:17   ` Adrian Bunk
2005-08-26 15:34     ` Danial Thom
2005-08-26 16:21       ` Adrian Bunk
2005-08-26 17:06         ` Danial Thom
2005-08-26 18:30           ` Adrian Bunk
2005-08-26 21:09             ` Danial Thom
2005-08-26 23:27               ` Ben Greear
2005-08-27 14:44                 ` Danial Thom [this message]
     [not found] <9a87484905082111205d27c1aa@mail.gmail.com>
2005-08-21 20:21 ` Danial Thom
2005-08-21 21:21   ` Jesper Juhl
2005-08-22 11:46   ` Denis Vlasenko
2005-08-21 17:07 Danial Thom
  -- strict thread matches above, loose matches on Subject: below --
2005-08-21 16:57 Danial Thom
2005-08-23  7:12 ` Helge Hafting
2005-08-23 17:10   ` Danial Thom
2005-08-23 17:21     ` Patrick McHardy
2005-08-24 16:24       ` Danial Thom
2005-08-24 16:35         ` Jesper Juhl
2005-08-24 17:26           ` Danial Thom
2005-08-25  4:51             ` Ben Greear
2005-08-25  6:08               ` Danial Thom
2005-08-25  6:15                 ` Ben Greear
2005-08-26  3:29                   ` Danial Thom
2005-08-26 22:18                     ` Danial Thom
2005-08-25  6:34                 ` Ben Greear
2005-08-25 14:26                   ` Danial Thom
2005-08-25 16:55                     ` Ben Greear
2005-08-25 20:45                       ` Danial Thom
2005-08-26 19:10                       ` Benjamin LaHaise
2005-08-27 11:19                 ` Vladimir B. Savkin
2005-08-27 14:35                   ` Danial Thom
2005-08-23 18:02     ` Sven-Thorsten Dietrich
2005-08-23 20:10       ` Danial Thom
2005-08-23 20:22         ` Sven-Thorsten Dietrich
2005-08-24 16:33           ` Danial Thom
2005-08-23 20:40         ` Patrick McHardy
2005-08-23 23:29           ` Ben Greear
2005-08-24 16:39           ` Danial Thom
2005-08-23 21:32     ` Jesper Juhl
2005-08-24 17:03       ` Danial Thom
2005-08-21 15:46 Danial Thom
2005-08-21 16:15 ` Patrick McHardy
2005-08-21 16:18   ` Danial Thom
2005-08-21 16:36     ` Patrick McHardy
2005-08-21 19:47 ` Andrew Morton

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=20050827144459.66078.qmail@web33304.mail.mud.yahoo.com \
    --to=danial_thom@yahoo.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@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

Powered by JetHome