From: markw@osdl.org
To: reiser@namesys.com
Cc: Nikita@namesys.com, Reiserfs-Dev@namesys.com,
Reiserfs-List@namesys.com, Linux-Kernel@Vger.Kernel.ORG,
cliff@lindows.com, tom.welch@lindows.com, garloff@suse.de,
drobbins@gentoo.org, reiserrf@hotmail.com
Subject: Re: Reiser4 needs more testers
Date: Mon, 29 Mar 2004 13:29:20 -0800 (PST) [thread overview]
Message-ID: <200403292129.i2TLTN204307@mail.osdl.org> (raw)
In-Reply-To: <40687354.1060604@namesys.com>
It's an OLTP database workload, but it is the one with all those fsyncs
that Nikita pointed out.
Mark
On 29 Mar, Hans Reiser wrote:
> This was the parallel fsync benchmark?
>
> Hans
>
> markw@osdl.org wrote:
>
>>I've run through another test on STP with the latest snapshot against
>>reiser4 and reiserfs for comparison. Reiser4 still seems to be lagging
>>behind reiserfs in our DBT-2 workload (the bigger number is better in
>>the metric):
>>
>> metric url to test results
>> ------ ---------------------------------
>>reiser4 1208 http://khack.osdl.org/stp/290774/
>>reiserfs 1819 http://khack.osdl.org/stp/290775/
>>
>>Mark
>>
>>On 26 Mar, Hans Reiser wrote:
>>
>>
>>>We have one NFS related bug remaining, and one mmap all of memory
>>>related bug (and performance issue) that you can hit using iozone. We
>>>will fix both of these in next week's snapshot, they were both multi-day
>>>bug fixes. When they are fixed, unless users/distros find bugs next
>>>week we will submit it for inclusion in the -mm and then the official
>>>kernel.
>>>
>>>We hope it is now fairly stable for average users if you avoid those two
>>>issues (we need to get rid of those dire warnings about its
>>>stability...., we will remember that next snapshot....;-) )
>>>
>>>We need a lot more real user testers, because we have run out of scripts
>>>that can crash it, and there are distros that would like to ship it
>>>soon. Please also complain to vitaly@namesys.com and ramon@namesys.com
>>>about poor documentation, etc., ....
>>>
>>>The new reiser4 snapshot (against 2.6.5-rc2) is available at
>>>
>>>http://www.namesys.com/snapshots/2004.03.26/
>>>
>>>
>>
>>
>>
>>
>>
>
>
next prev parent reply other threads:[~2004-03-29 21:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 16:45 [ANNOUNCE] new reiser4 snapshot released Nikita Danilov
2004-03-26 17:05 ` Reiser4 needs more testers Hans Reiser
2004-03-26 19:32 ` Dr. Giovanni A. Orlando
2004-03-29 16:59 ` markw
2004-03-29 19:04 ` Hans Reiser
2004-03-29 21:29 ` markw [this message]
2004-03-26 17:23 ` [ANNOUNCE] new reiser4 snapshot released Jonathan Briggs
2004-03-26 18:11 ` Nikita Danilov
2004-03-26 17:11 ` Hans Reiser
2004-03-27 12:32 ` [OT] Re[2]: " Maciej Soltysiak
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=200403292129.i2TLTN204307@mail.osdl.org \
--to=markw@osdl.org \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=Nikita@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=cliff@lindows.com \
--cc=drobbins@gentoo.org \
--cc=garloff@suse.de \
--cc=reiser@namesys.com \
--cc=reiserrf@hotmail.com \
--cc=tom.welch@lindows.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