All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Ryan Earl" <heretic@clanhk.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fw: Performance drop 2.6.0-test7 -> 2.6.1-rc2
Date: Thu, 08 Jan 2004 14:20:49 +0000	[thread overview]
Message-ID: <3FFD6741.3000300@clanhk.org> (raw)
In-Reply-To: <20040108023356.00db9dec.akpm@osdl.org>

Andrew Morton wrote:

>Jan Kasprzak <kas@informatics.muni.cz> wrote:
>  
>
>>Andrew Morton wrote:
>>: Jan Kasprzak <kas@informatics.muni.cz> wrote:
>>: >  - this is reliable: repeated boot back to 2.6.1-rc2 makes the problem
>>: >  	appear again (high load, system slow has hell), booting back
>>: >  	to -test7 makes it disappear.
>>    
>>

I was about to post something about this as well.  I recently went to 
upgrade a production server in a datacenter.  I wanted to use a 2.6 
kernel: I tried 2.6.0-mm1 and 2.6.1-rc1-mm1--needed the siimage 
patches.  User space CPU usage was WAY high.  I'm talking 2x or more 
than normal, though sys time was low.  Processes that had no connections 
and should have used 0% CPU were using 1% CPU when no one was even 
connected.  And a loaded process which should only use ~25% CPU was 
using 60% CPU.  Very unresponsive, very slow.  I ended up staying with a 
2.4.23 kernel with my required patches.  I didn't try any other 2.6 
kernels, so I can't say which version this problem appeared in, but I 
DEFINITELY noticed it and it is repeatable.  I didn't have time to test 
further.

-ryan



  parent reply	other threads:[~2004-01-08 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040107023042.710ebff3.akpm@osdl.org>
2004-01-07 21:52 ` Fw: Performance drop 2.6.0-test7 -> 2.6.1-rc2 Nathan Scott
2004-01-08  9:54   ` Jan Kasprzak
2004-01-08 10:16     ` Andrew Morton
2004-01-08 10:25       ` Jan Kasprzak
2004-01-08 10:33         ` Andrew Morton
2004-01-08 11:01           ` Jan Kasprzak
2004-01-08 14:20           ` J. Ryan Earl [this message]
2004-01-08 12:07     ` Christoph Hellwig
2004-01-08 15:03       ` Jan Kasprzak
2004-01-08 15:11         ` Jan Kasprzak

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=3FFD6741.3000300@clanhk.org \
    --to=heretic@clanhk.org \
    --cc=akpm@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.