mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: wli@holomorphy.com, akpm@digeo.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.46-mm2
Date: Sun, 10 Nov 2002 23:37:25 -0500 (EST)	[thread overview]
Message-ID: <200211110437.gAB4bPl390685@saturn.cs.uml.edu> (raw)


William Lee Irwin III writes:
> On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:

>> It could be the procps thing?  `tiobench --threads 256' shows
>> up as a single process in top and ps due to the new thread
>> consolidation feature. If you run `ps auxm' or hit 'H' in top,
>> all is revealed.  Not my fave feature that.

The feature is both buggy (both false consolidation and failure
to consolidate) and slow. While I do eventually need to add the
feature, I'm not doing so until it can be implemented properly.
So go ahead and enjoy procps-3.1.0 without it:

http://procps.sf.net/

Future-compatibility exists. The "m" and "-m" options are currently
ignored so that you may use them in scripts without causing errors.

Um, BTW, don't we need /proc/42/threads/123/stat and friends
before the Linux 2.6.xx release? Without them, the new clone
flags supposedly let a user hide a task. That's really bad.

> Turns out monitoring things via /proc/ slowed it down by
> some ridiculous factor while it was trying to spawn threads.
> 9 hours became less than 1s when I stopped looking.

Not that procps will ever be fast, but 3.1.0 is a lot faster
than 2.x.xx is. Five out of the last seven releases have
included performance improvements, and more are coming.

You also get IO-wait info in vmstat. Upgrade today! :-)

             reply	other threads:[~2002-11-11  4:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11  4:37 Albert D. Cahalan [this message]
2002-11-11  7:43 ` 2.5.46-mm2 William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2002-11-10  3:59 2.5.46-mm2 Andrew Morton
2002-11-10 14:32 ` 2.5.46-mm2 Jens Axboe
2002-11-10 14:52   ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 14:57     ` 2.5.46-mm2 Jens Axboe
2002-11-10 15:06       ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 15:58         ` 2.5.46-mm2 Jens Axboe
2002-11-10 19:39           ` 2.5.46-mm2 Andrew Morton
2002-11-11  1:18             ` 2.5.46-mm2 William Lee Irwin III
2002-11-11  7:04             ` 2.5.46-mm2 Jens Axboe
2002-11-11  7:41               ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 16:58         ` 2.5.46-mm2 Andrew Morton
2002-11-10 17:11           ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 23:10             ` 2.5.46-mm2 Toon van der Pas

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=200211110437.gAB4bPl390685@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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

all inboxes | Powered by JetHome®