mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: markw@osdl.org
To: Nikita@Namesys.COM
Cc: piggin@cyberone.com.au, reiserfs-list@Namesys.COM,
	linux-kernel@vger.kernel.org
Subject: Re: AS performance with reiser4 on 2.6.3
Date: Fri, 27 Feb 2004 08:56:17 -0800 (PST)	[thread overview]
Message-ID: <200402271656.i1RGuME16838@mail.osdl.org> (raw)
In-Reply-To: <16446.13520.5837.193556@laputa.namesys.com>

On 26 Feb, Nikita Danilov wrote:
> markw@osdl.org writes:
>  > Hi Nick,
>  > 
>  > I started getting some results with dbt-2 on 2.6.3 and saw that reiser4
>  > is doing a bit worse with the AS elevator.  Although reiser4 wasn't
>  > doing well to begin with, compared to the other filesystems.  I have
>  > links to the STP results on our 4-ways and 8-ways here:
>  > 	http://developer.osdl.org/markw/fs/dbt2_stp_results.html
> 
> There were no changes between 2.6.2 and 2.6.3 that could affect reiser4
> performance, so it is not clear why numbers are so different. Probably
> results should be averaged over several runs. Also can you run test with
> 
> http://www.namesys.com/snapshots/2004.02.25/extra/e_05-proc-sleep.patch
> 
> applied? To use it turn CONFIG_PROC_SLEEP on (depends on
> CONFIG_FRAME_POINTER), and do "cat /proc/sleep" before and after test
> run.

http://khack.osdl.org/stp/288905/results/

There are a set of /proc/sleep files there from a 4-way system.

Mark

  parent reply	other threads:[~2004-02-27 16:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26 17:48 markw
2004-02-26 18:02 ` Nikita Danilov
2004-02-27  3:37   ` Hans Reiser
2004-02-27 10:43     ` Dr. Giovanni A. Orlando
2004-02-27 17:03     ` markw
2004-02-27 17:18       ` Nikita Danilov
2004-02-27 18:57         ` Hans Reiser
2004-02-27 16:56   ` markw [this message]
2004-02-27 18:25     ` Nikita Danilov
2004-03-02 17:07       ` markw

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=200402271656.i1RGuME16838@mail.osdl.org \
    --to=markw@osdl.org \
    --cc=Nikita@Namesys.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®