All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Cc: Chris Mason <mason@suse.com>, reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: [PATCH] new data logging and quota patches available
Date: Wed, 12 Mar 2003 22:25:16 +0300	[thread overview]
Message-ID: <3E6F899C.8090108@namesys.com> (raw)
In-Reply-To: <3E6F4777.1040802@mb.tu-ilmenau.de>

Manuel Krause wrote:

> On 03/11/2003 09:46 PM, Chris Mason wrote:
>
>> [ slow down between 2.419 data logging and 2.4.21-pre data logging ]
>>
>> Ok, could you please apply the search_reada-4 patch I sent and do your
>> benchmark again on 2.4.21-preX with these mount options:
>>
>> mount -o alloc=old_way:concentrating_formatted_nodes,notail
>>
>> It's about 10% faster here, but my dataset is slightly different.
>>
>
> I did it and also tested without the alloc mount option from above.
>
> Here is the overview including the "old" things to refer to. The 
> dataset didn't change in the meantime.
>
> (old)
> 2.4.21-pre5 data=ordered                              [A]
>       first run  second run  diff  average    rate
> real  9m05.375s   9m23.272s  3.2%  9m14.324s  6.63MB/s
> user  0m01.440s   0m01.730s
> sys   1m11.640s   1m08.870s
>
> 2.4.19 data=ordered                                   [B]
>       first run  second run  diff  average    rate
> real  7m46.287s   7m34.031s  2.7%  7m40.159s  7.99MB/s
> user  0m01.520s   0m01.580s
> sys   1m21.920s   1m21.300s
>
>
> (new)
> 2.4.21-pre5 [A] + search_reada-4 +
> mount -o noatime,alloc=old_way:concentrating_formatted_nodes,notail [C]
>
>       first run second run  diff   average    rate
> real  7m59.631s  7m57.167s  0.52%  7m58.399s  7.68MB/s
> user  0m01.580s  0m01.250s
> sys   1m11.200s  1m09.520s
>
>
> 2.4.21-pre5 [A] + search_reada-4 without special mount options
> (is: mount -o noatime,notail,data=ordered)                          [D]
>
>       first run second run  diff   average    rate
> real  7m57.365s  7m55.638s  0.36%  7m56.502s  7.71MB/s
> user  0m01.510s  0m01.570s
> sys   1m07.730s  1m08.020s
>
>
> * What means a performance increase of 2.4.21-pre5 with [D] vs. without
>    search_reada-4 [A] by  ~16%  !!!
> * The difference of the special mount option [C] against my default [D]
>   is about 0.3%  ;-))
> * With search_reada-4  2.4.21-pre5 [D] only looses ~3.6% throughput rate
>    against 2.4.19 [B]
>  ...in this test.
>
>
> Do you think the group-alloc-4 patch would increase throughput with 
> this test?
>
> Thank you for your great work,
>
> Manuel
>
>
>
>
>
Can you state what test is being performed, what the hardware is, etc.  
In general, we need benchmarks that can be collected onto webpages and 
reviewed a year or two later when we can barely remember why we did or 
did not do some design decision.

-- 
Hans



  parent reply	other threads:[~2003-03-12 19:25 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21 23:32 [PATCH] new data logging and quota patches available Chris Mason
2003-02-21 23:52 ` Philippe Gramoullé
2003-02-22 12:41 ` Dieter Nützel
2003-02-22 15:15   ` Chris Mason
2003-02-22 16:12     ` Chris Mason
2003-02-23  0:50       ` Manuel Krause
2003-02-23  1:04         ` Manuel Krause
2003-02-23 14:50           ` Chris Mason
2003-02-23 17:18           ` Chris Mason
2003-02-23 17:37             ` Marc-Christian Petersen
2003-02-23 18:39               ` Marc-Christian Petersen
2003-02-23 19:33                 ` Chris Mason
2003-02-24 18:01                   ` Marc-Christian Petersen
2003-02-24  1:42             ` Manuel Krause
2003-02-24 14:08               ` Chris Mason
2003-02-24 17:45                 ` Manuel Krause
2003-02-24 22:19                   ` Manuel Krause
2003-02-28  8:10                     ` Manuel Krause
2003-02-28 13:32                       ` Chris Mason
2003-03-06  2:49                         ` Manuel Krause
2003-03-06  3:46                           ` Chris Mason
2003-03-06  4:03                             ` Manuel Krause
2003-03-08 14:13                               ` Manuel Krause
2003-03-09 16:39                                 ` Chris Mason
2003-03-09 17:07                                   ` Manuel Krause
2003-03-09 17:24                                     ` Chris Mason
2003-03-09 17:39                                       ` Manuel Krause
2003-03-09 18:12                                         ` Chris Mason
2003-03-11  1:42                                         ` Chris Mason
2003-03-11 20:46                                         ` Chris Mason
2003-03-12  7:38                                           ` Oleg Drokin
2003-03-12 13:22                                             ` Chris Mason
2003-03-12 13:28                                               ` Oleg Drokin
2003-03-12 13:41                                                 ` Chris Mason
2003-03-12 14:43                                           ` Manuel Krause
2003-03-12 14:55                                             ` Chris Mason
2003-03-12 19:25                                             ` Hans Reiser [this message]
2003-03-13  2:01                                               ` Manuel Krause
2003-02-24 17:59               ` Marc-Christian Petersen
2003-02-24 18:05                 ` Marc-Christian Petersen
2003-02-24 18:46                   ` Chris Mason
2003-02-24 18:08                 ` Chris Mason
2003-02-24 18:11                   ` Marc-Christian Petersen
2003-02-23 14:56         ` Chris Mason
2003-02-22 13:54 ` Oleg Drokin
2003-02-22 14:17   ` Chris Mason
2003-02-25 15:31   ` Ookhoi

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=3E6F899C.8090108@namesys.com \
    --to=reiser@namesys.com \
    --cc=manuel.krause@mb.tu-ilmenau.de \
    --cc=mason@suse.com \
    --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.