All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jindrich Makovicka <makovick@kmlinux.fjfi.cvut.cz>
To: Hans Reiser <reiser@namesys.com>
Cc: Laurent Riffard <laurent.riffard@free.fr>,
	reiserfs-list@namesys.com, vs <vs@thebsh.namesys.com>,
	Alexander Zarochentcev <zam@namesys.com>
Subject: Re: 2.6.16-rc6-mm2: slow writes on reiser4.
Date: Thu, 23 Mar 2006 19:44:56 +0100	[thread overview]
Message-ID: <4422ECA8.6000309@kmlinux.fjfi.cvut.cz> (raw)
In-Reply-To: <44219FA8.2050606@namesys.com>

Hans Reiser wrote:
> Instead of using sync, could you increase the size of the files you
> write so that they are 10x ram size?
> 
> I have a suspicion we are slow at sync....  I am not sure why, but I
> have seen other data where sync was slow for us, and maybe we need to
> optimize that code path.

My impression is rather that the bottleneck is the amount of seeking the
sync causes - would it be possible to reorder the write operations
somehow, still preserving atomicity?

Also, a comparison of Reiser4 performance on NCQ vs. non-NCQ drive could
be interesting (I don't have NCQ, maybe that's the problem).

Regards,
-- 
Jindrich Makovicka

  reply	other threads:[~2006-03-23 18:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 21:16 2.6.16-rc6-mm2: slow writes on reiser4 Laurent Riffard
2006-03-22  7:41 ` Hans Reiser
2006-03-22 18:51   ` Laurent Riffard
2006-03-22 19:04     ` Hans Reiser
2006-03-23 18:44       ` Jindrich Makovicka [this message]
2006-03-23 21:32         ` Nate Diller
2006-03-28 20:19       ` Laurent Riffard
2006-03-28 20:34         ` Hans Reiser
2006-03-28 20:56           ` Hans Reiser
2006-03-28 22:49         ` Philippe Gramoullé
2006-03-29  6:16           ` Laurent Riffard
2006-03-29 14:30             ` Philippe Gramoullé
2006-04-01 23:15   ` Pierre Etchemaïté
2006-03-22 17:48 ` Laurent Riffard

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=4422ECA8.6000309@kmlinux.fjfi.cvut.cz \
    --to=makovick@kmlinux.fjfi.cvut.cz \
    --cc=laurent.riffard@free.fr \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@thebsh.namesys.com \
    --cc=zam@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 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.