All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Saveliev <vs@namesys.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: reiserfs-list@namesys.com, reiserfs-dev@namesys.com
Subject: Re: dbench regression in 2.6
Date: Mon, 8 Sep 2003 21:05:37 +0400	[thread overview]
Message-ID: <200309082105.37309.vs@namesys.com> (raw)
In-Reply-To: <3F574AEE.7080402@austin.ibm.com>

Hi

On Thursday 04 September 2003 18:23, Steven Pratt wrote:
> Vladimir Saveliev wrote:
> 
> >Hi
> >
> >On Wednesday 03 September 2003 23:04, Hans Reiser wrote:
> >  
> >
> >>Steven Pratt wrote:
> >>
> >>    
> >>
> >>>Is anyone looking into the dbench multitheaded regression in 2.6 that I 
> >>>reported here a couple of weeks ago? 
> >>>      
> >>>
> >
> >Sorry, I was unable to find your report in mail archives. Could you, 
please, 
> >remind what is the problem?
> >
> > I don't see any change in the 
> >  
> >
> >>>latest trees.
> >>>
> >>>      
> >>>
> The problem showed up in 2.6.0-test1, and every kernel since.  The 
> problem is that from 2.5.65 (earliest data I have) to 2.5.69 dbench on 
> reiserfs with 16 clients got a throughput of ~200MB/sec.  In 2.5.70 
> through 2.5.75 the score went up to ~280MB/sec, a good thing.  But in 
> 2.6.0-test1 the throughput dropped to below 50 MB/sec.  Since then it 
> has risen slightly but still at only around 60MB/sec.  Single client 
> dbench showed similar, although much less dramatic changes.  No other 
> file system exhibited a change in the 2.6.0-test1 kernel so this seems 
> to be unique to reiserfs.
> 
> 
> >>>      
> >>>
> 
>http://ausgsa.ibm.com/projects/l/ltcperformance/2003benchmarks/regression/results/history-graphs/dbench.reiser.throughput.plot.16.png
> >  
> >
> >
> >Is this address right?
> >
> No, my bad.  Right address is 
> 
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/dbench.reiser.throughput.plot.16.png
> see also
> 
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/dbench.reiser.throughput.plot.1.png
> 
> Also if you go to
> 
http://ltcperf.ncsa.uiuc.edu/data/2.6.0-test1/2.5.75-vs-2.6.0-test1/index.html
> and select the results links related to dbench resierfs you can find 
> kernel profile, sar data and lots of other system information which may 
> help in isolating the problem.
> 
> Steve
> 

Unfortunately, I was unable to reproduce your result. On our test machine (4 
Xeons 1gb ram) results shown by reiserfs on 2.5.75 and 2.6.0-test1 are 
comparable.

So, would be you so kind to help us to track this issue? If yes, could you , 
please, describe your test in more details.
0. what is version of dbench you used: 1.2, 1.3 or 2.0?
1. how many time did you run dbench 16?
2. when did you mkfs, etc, did you reboot after mkfs?
3. how much ram does machine which was running dbench have?
4. could you please try to rerun benchmark with SMP=off, and with 2 and 4 
cpus?
5. could you also run dbench 64 and dbench 128 for reiserfs 2.5.75 and 
2.6.0-test1?

Thanks,
vs




> 
> 
> 


  parent reply	other threads:[~2003-09-08 17:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03 18:46 dbench regression in 2.6 Steven Pratt
2003-09-03 19:43 ` Mike Fedyk
2003-09-03 22:42 ` Mike Fedyk
2003-09-04 14:13   ` Steven Pratt
     [not found] ` <3F563B3B.6060406@namesys.com>
2003-09-04  7:38   ` Vladimir Saveliev
2003-09-04 14:23     ` Steven Pratt
2003-09-04 17:58       ` Mike Fedyk
2003-09-05 15:24         ` Steven Pratt
2003-09-05 15:49           ` Hans Reiser
2003-09-08 17:05       ` Vladimir Saveliev [this message]
2003-09-08 18:02         ` Steven Pratt
2003-09-08 19:55         ` Steven Pratt
2003-09-08 20:10           ` Hans Reiser
2003-09-08 20:34             ` Steven Pratt
2003-09-09 10:35           ` Nikita Danilov

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=200309082105.37309.vs@namesys.com \
    --to=vs@namesys.com \
    --cc=reiserfs-dev@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=slpratt@austin.ibm.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.