From: Con Kolivas <conman@kolivas.net>
To: linux-kernel@vger.kernel.org
Cc: Paolo Ciarrocchi <ciarrocchi@linuxmail.org>
Subject: Re: [Benchmark] Contest 0.51
Date: Sun, 13 Oct 2002 09:49:46 +1000 [thread overview]
Message-ID: <200210130949.52013.conman@kolivas.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>It seems useful to me add a colum with CPU%+LCPU%.
>It is intersting to notice that 2.5.41 spend 41+9=50% CPU time
>for compiling and for the io_load while 2.5.42 spend 45+9=54%
>time. Can I say that 2.5.42 is "better" than 2.5.41 ?
No I'm afraid not. The lcpu% cant estimate accurately the cpu% used by the
load while the kernel is actually being compiled as the load starts before
ther kernel compilation and ends after it. This means that lcpu% will always
overestimate the loads' cpu%. I haven't found a workaround for this... yet
Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9qLUdF6dfvkL3i1gRAmS/AJ49q1Kd1RBZU8bflVd2n5RUi1Q3UQCffNZI
8V14Cm2/xbXk/QMCCoBnIf4=
=/fVc
-----END PGP SIGNATURE-----
next reply other threads:[~2002-10-12 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 23:49 Con Kolivas [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-12 23:18 [Benchmark] Contest 0.51 Paolo Ciarrocchi
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=200210130949.52013.conman@kolivas.net \
--to=conman@kolivas.net \
--cc=ciarrocchi@linuxmail.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.