From: Delian Krustev <krustev-sueGvCUcFGXR7s880joybQ@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Performance problems over AoE
Date: Mon, 21 Dec 2009 18:21:39 +0200 [thread overview]
Message-ID: <200912211821.45366.krustev@krustev.net> (raw)
In-Reply-To: <20091219.184346.239007912.ryusuke-sG5X7nlA6pw@public.gmane.org>
Hi,
Thanks for the answers.
On Sat, 19 Dec 2009 18:43:46 +0900 (JST) Ryusuke Konishi wrote:
> Thank you for letting us know the interesting measurement result.
>
> Actually we recognize similar issue on high performance drives, but
> this looks worse than the cases we know.
This might be due to the increased latency of the AoE device.
> In the 2.6.33 merge window, I sent some series of patches upstream to
> improve write performance. And, the effort is still going on.
>
> I would appreciate it if you could try nilfs in kernel 2.6.33-rc1 or
> optimization patches that will be appeared ongoingly in this list or
> linux-nilfs.
OK, I will try it. Just have to figure out on which hardware since the
setup I've described is on production systems and running early RC kernels
there is not an option.
But I will probably find the metal or will create some VM images.
> Unfortunately no. The contiguous check point creation is what nilfs
> stands for. But, I think the performance impact of cp creation is not
> so high unless you are doing osync writes.
Did you read the part for the cleanerd causing high load on the network
interface ?
And the checkpoints being created with no data modifications ?
Do you have a guess for these ?
Cheers
--
Delian
next prev parent reply other threads:[~2009-12-21 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 0:24 Performance problems over AoE Delian Krustev
[not found] ` <200912190224.46774.krustev-sueGvCUcFGXR7s880joybQ@public.gmane.org>
2009-12-19 9:43 ` Ryusuke Konishi
[not found] ` <20091219.184346.239007912.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-12-21 16:21 ` Delian Krustev [this message]
[not found] ` <200912211821.45366.krustev-sueGvCUcFGXR7s880joybQ@public.gmane.org>
2009-12-21 18:46 ` Ryusuke Konishi
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=200912211821.45366.krustev@krustev.net \
--to=krustev-suegvcucfgxr7s880joybq@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
/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.