From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Reading /proc/stat is slooow
Date: Fri, 02 Dec 2005 17:42:49 +0000 [thread overview]
Message-ID: <je1x0v4cpy.fsf@sykes.suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
At some point after 2.6.13 reading /proc/stat has become too slow. This
is most visible with xosview, which spends up to 80% in kernel space. I
have attached a simple program that you can run with "strace -r" to see
that the second read of /proc/stat which eventually returns EOF takes too
much time. If you remove the loop around read the same amount of time is
now spent in close.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
[-- Attachment #2: stat.c --]
[-- Type: text/plain, Size: 300 bytes --]
#include <unistd.h>
#include <fcntl.h>
static char buf[8192];
int
main (int argc, char **argv)
{
const char *file = argc > 1 ? argv[1] : "/proc/stat";
while (1)
{
int fd = open (file, O_RDONLY);
while (read (fd, buf, 8192) > 0);
close (fd);
usleep (300000);
}
}
next reply other threads:[~2005-12-02 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 17:42 Andreas Schwab [this message]
2005-12-05 22:21 ` Reading /proc/stat is slooow Luck, Tony
2005-12-05 23:36 ` Andreas Schwab
2005-12-05 23:46 ` Andreas Schwab
2005-12-06 0:19 ` Luck, Tony
2005-12-06 1:21 ` Luck, Tony
2005-12-06 6:15 ` Luck, Tony
2005-12-06 9:24 ` Zou, Nanhai
2005-12-06 16:58 ` Luck, Tony
2005-12-06 17:10 ` Andreas Schwab
2005-12-07 19:54 ` [PATCH] Drop per-irq counters from /proc/stat (Was: Reading /proc/stat is slooow) Luck, Tony
2005-12-06 9:57 ` Reading /proc/stat is slooow Andreas Schwab
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=je1x0v4cpy.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-ia64@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