public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. Giovanni A. Orlando" <gorlando@futuretg.com>
To: unlisted-recipients:; (no To-header on input)
Cc: markw@osdl.org, Carl Johnson <cjohnson@osdl.org>,
	Hans Reiser <reiser@namesys.com>,
	reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: AS performance with reiser4 on 2.6.3
Date: Fri, 27 Feb 2004 11:43:42 +0100	[thread overview]
Message-ID: <403F1F5E.9000704@futuretg.com> (raw)
In-Reply-To: <403EBB87.2070504@namesys.com>

Dear Mark,

    I appreciate the OSDL efforts and graphs you offer for ReiserFS 4, 
but I will
    appreciate a lot more if you adopt a distro that adopt ReiserFS 
like: SuSE, Lindows or our FTOSX.

    For us ReiserFS is important for RedHat really don't.

    So, I don't want to see again the RedHat 9, name here:
       http://developer.osdl.org/markw/fs/dbt2_stp_results.html

Thanks very much,
Giovanni

> 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.
>>
> The differences don't "feel" like testing error, and in any event 
> something is seriously wrong.  That something is either poor fsync 
> performance, or poor scalability.  In any event, please investigate, 
> and please try such things as using capture on copy.  Mark, does this 
> benchmark like to use fsync?
>
> Thanks much mark for bringing this to our attention.
>
>> 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.
>>
>> > > -- > Mark Wong - - markw@osdl.org
>>
>> Nikita.
>> -
>> To unsubscribe from this list: send the line "unsubscribe 
>> linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
>>
>>
>>  
>>
>
>


  reply	other threads:[~2004-02-27 10:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26 17:48 AS performance with reiser4 on 2.6.3 markw
2004-02-26 18:02 ` Nikita Danilov
2004-02-27  3:37   ` Hans Reiser
2004-02-27 10:43     ` Dr. Giovanni A. Orlando [this message]
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
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=403F1F5E.9000704@futuretg.com \
    --to=gorlando@futuretg.com \
    --cc=cjohnson@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markw@osdl.org \
    --cc=reiser@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox