From: Brian McGroarty <brian@mcgroarty.net>
To: Albert Cahalan <albert@users.sf.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: /proc reliability & performance
Date: Thu, 16 Oct 2003 22:24:36 -0500 [thread overview]
Message-ID: <20031017032436.GA17480@mcgroarty.net> (raw)
In-Reply-To: <1066356438.15931.125.camel@cube>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
On Thu, Oct 16, 2003 at 10:07:18PM -0400, Albert Cahalan wrote:
> I created a process with 360 thousand threads,
> went into the /proc/*/task directory, and did
> a simple /bin/ls. It took over 9 minutes on a
> nice fast Opteron. (it's the same at top-level
> with processes, but I wasn't about to mess up
> my system that much)
Are there many cases where the /proc directory contents are read in
this fashion?
I'd be more curious about how performance fares with reading a
thousand entries by name with 1k processes and with 360k processes.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-17 3:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 2:07 /proc reliability & performance Albert Cahalan
2003-10-17 2:34 ` Larry McVoy
2003-10-17 8:01 ` dada1
2003-10-17 9:10 ` David S. Miller
2003-10-17 14:46 ` Valdis.Kletnieks
2003-10-17 17:24 ` dada1
2003-10-17 23:48 ` Albert Cahalan
2003-10-18 6:35 ` Willy Tarreau
2003-10-18 6:38 ` David S. Miller
2003-10-17 2:51 ` William Lee Irwin III
2003-10-17 3:24 ` Brian McGroarty [this message]
2003-10-17 4:31 ` Albert Cahalan
2003-10-17 4:56 ` William Lee Irwin III
2003-10-17 8:21 ` David Rees
2003-10-17 7:40 ` Zan Lynx
2003-10-17 7:54 ` William Lee Irwin III
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=20031017032436.GA17480@mcgroarty.net \
--to=brian@mcgroarty.net \
--cc=albert@users.sf.net \
--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.