mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: markw@osdl.org
To: reiser@namesys.com
Cc: Nikita@namesys.com, 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 09:03:58 -0800 (PST)	[thread overview]
Message-ID: <200402271704.i1RH45E19258@mail.osdl.org> (raw)
In-Reply-To: <403EBB87.2070504@namesys.com>

On 27 Feb, Hans Reiser wrote:
> 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.

Yes, PostgreSQL uses fsync for its database logging.  I can certainly
enable the capture on copy option.  Does that produce something that I
need to manually capture?

Mark

  parent reply	other threads:[~2004-02-27 17:04 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 [this message]
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=200402271704.i1RH45E19258@mail.osdl.org \
    --to=markw@osdl.org \
    --cc=Nikita@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    --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

all inboxes | Powered by JetHome®