All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paolo Ciarrocchi" <ciarrocchi@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: [Benchmark] Contest results (2.4.19 2.5.47 .48 .49)
Date: Mon, 25 Nov 2002 02:25:39 +0800	[thread overview]
Message-ID: <20021124182539.31423.qmail@linuxmail.org> (raw)

$ cat /cygdrive/log/results.log

noload:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [1]              133.3   98      0       0       1.00
2.5.47 [1]              138.3   96      0       0       1.04
2.5.48 [1]              138.0   96      0       0       1.03
2.5.49 [1]              137.9   96      0       0       1.03

process_load:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [1]              223.3   57      183     43      1.67
2.5.47 [1]              210.2   63      75      37      1.58
2.5.48 [1]              214.5   62      79      38      1.61
2.5.49 [1]              208.9   63      74      37      1.57

ctar_load:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [1]              169.8   80      3       9       1.27
2.5.47 [1]              170.8   82      3       9       1.28
2.5.48 [1]              170.7   82      3       9       1.28
2.5.49 [1]              171.4   82      3       9       1.29

xtar_load:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [1]              208.7   65      4       10      1.57
2.5.47 [1]              185.0   73      3       8       1.39
2.5.48 [1]              183.9   74      3       8       1.38
2.5.49 [1]              187.5   72      3       9       1.41

io_load:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [1]              961.5   14      100     13      7.21
2.5.47 [1]              254.9   54      22      12      1.91
2.5.48 [1]              220.8   62      18      12      1.66
2.5.49 [1]              224.8   60      20      13      1.69

read_load:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [1]              189.2   72      15      5       1.42
2.5.47 [1]              167.5   82      10      5       1.26
2.5.48 [1]              168.8   82      13      6       1.27
2.5.49 [1]              167.4   82      11      5       1.26

list_load:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [1]              149.1   89      0       6       1.12
2.5.47 [1]              158.7   85      0       9       1.19
2.5.48 [1]              158.3   85      0       9       1.19
2.5.49 [1]              156.6   86      0       9       1.17

mem_load:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [1]              174.0   77      39      1       1.30
2.5.47 [1]              205.8   66      39      1       1.54
2.5.48 [1]              166.1   82      34      1       1.25
2.5.49 [1]              172.5   79      36      1       1.29
-- 
______________________________________________
http://www.linuxmail.org/
Now with POP3/IMAP access for only US$19.95/yr

Powered by Outblaze

                 reply	other threads:[~2002-11-24 18:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021124182539.31423.qmail@linuxmail.org \
    --to=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.