From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
krustev-sueGvCUcFGXR7s880joybQ@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Performance problems over AoE
Date: Sat, 19 Dec 2009 18:43:46 +0900 (JST) [thread overview]
Message-ID: <20091219.184346.239007912.ryusuke@osrg.net> (raw)
In-Reply-To: <200912190224.46774.krustev-sueGvCUcFGXR7s880joybQ@public.gmane.org>
Hi!
On Sat, 19 Dec 2009 02:24:44 +0200, Delian Krustev <krustev-sueGvCUcFGXR7s880joybQ@public.gmane.org> wrote:
>
> Hi All,
>
> Nice to meet you :-)
>
> I'm having performance problems with NILFS2 running on
> AoE (Ata over Ethernet) device.
>
> I'm able to get around 5/10 MB sequential write speed for over a device
> which is capable of 100MB/s.
>
> I've described the problem and my setup in details on a web page:
>
> http://krustev.net/w/articles/Backup_service_and_software_block_devices_over_the_net/
>
>
> and will be thankful if you take a look and give some ideas.
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.
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.
> And one other question.
> Is there a way to disable the auto check point creation ?
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.
> Cheers
> --
> Delian
Cheers,
Ryusuke Konishi
next prev parent reply other threads:[~2009-12-19 9:43 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 [this message]
[not found] ` <20091219.184346.239007912.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-12-21 16:21 ` Delian Krustev
[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=20091219.184346.239007912.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=krustev-sueGvCUcFGXR7s880joybQ@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox