All of lore.kernel.org
 help / color / mirror / Atom feed
From: camis <camis@mweb.co.za>
To: reiserfs-list@namesys.com
Subject: Re: reiserfs v3 patches updated
Date: Tue, 06 Apr 2004 21:17:02 +0200	[thread overview]
Message-ID: <4073022E.3090100@mweb.co.za> (raw)
In-Reply-To: <1081277245.30813.81.camel@watt.suse.com>

>>Has anyone done any throughput/benchmarks for the various
>>new patches/code?
> 
> The block allocator stuff is fresh from the oven and still warm inside. 
> I'll be posting benchmarks for it as the week goes on.

Something interesitng:
I have 8 dell 2650's (dual xeon 2.8ghz+hyperthreading) and i've setup
the one machine above with the patches.. All 8 machines are incoming
MX/smtp machines which handle quite large loads (5gigs of mail per day).

machine 1: 
(mounted:noatime,nodiratime,data=ordered,alloc=skip_busy:dirid_groups,packing_groups)

  21:16:17  up 12:17,  1 user,  load average: 0.45, 1.04, 1.07
375 processes: 374 sleeping, 1 running, 0 zombie, 0 stopped
CPU states:  cpu    user    nice  system    irq  softirq  iowait    idle
            total    7.2%    0.0%   32.4%   0.0%     0.8%    5.2%  353.2%
            cpu00    1.8%    0.0%   10.6%   0.1%     0.9%    1.3%   85.0%
            cpu01    1.5%    0.0%    7.4%   0.0%     0.1%    0.9%   89.9%
            cpu02    1.7%    0.0%    7.0%   0.0%     0.1%    1.7%   89.3%
            cpu03    1.8%    0.0%    7.4%   0.0%     0.1%    1.5%   88.9%

Iowait total stays hovering at around the 6->8% mark..

machine 2->8: (mounted: noatime,nodiratime)

  21:14:31  up 1 day,  8:41,  1 user,  load average: 0.43, 0.72, 0.66
392 processes: 391 sleeping, 1 running, 0 zombie, 0 stopped
CPU states:  cpu    user    nice  system    irq  softirq  iowait    idle
            total    8.0%    0.0%   35.2%   0.0%     1.6%    0.8%  352.8%
            cpu00    2.0%    0.0%   11.1%   0.1%     1.5%    0.3%   84.6%
            cpu01    2.0%    0.0%    7.7%   0.0%     0.3%    0.1%   89.5%
            cpu02    2.2%    0.0%    7.7%   0.0%     0.0%    0.3%   89.5%
            cpu03    1.8%    0.0%    8.7%   0.0%     0.0%    0.0%   89.3%

The majority of the rest of the machines iowait hover around the 1%
mark.. CPU time tends to be about the same, just the iowait is much
much higher..

Cami

  reply	other threads:[~2004-04-06 19:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  0:10 reiserfs v3 patches updated Chris Mason
2004-04-06 16:38 ` Christian Mayrhuber
2004-04-06 16:48   ` Chris Mason
2004-04-06 18:29   ` camis
2004-04-06 18:47     ` Chris Mason
2004-04-06 19:17       ` camis [this message]
2004-04-06 19:24         ` Chris Mason
2004-04-06 19:53           ` camis
2004-04-06 20:29             ` Chris Mason
2004-04-06 20:38               ` Cami
2004-04-06 20:33             ` Chris Mason
2004-04-06 20:51               ` Cami
2004-04-06 21:10                 ` Chris Mason
2004-04-06 21:30                   ` Cami
2004-04-06 21:39                     ` Chris Mason
2004-04-07  9:28   ` reiserfs v3 patches updated - Bug Christian Mayrhuber
2004-04-07 13:07     ` Chris Mason
     [not found]       ` <200404071714.39187.christian.mayrhuber@gmx.net>
2004-04-07 23:58         ` Chris Mason
2004-04-13 14:57           ` Christian Mayrhuber
2004-04-10 22:53 ` reiserfs v3 patches updated Hubert Chan

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=4073022E.3090100@mweb.co.za \
    --to=camis@mweb.co.za \
    --cc=reiserfs-list@namesys.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 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.