Linux NILFS development
 help / color / mirror / Atom feed
From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: Low nilfs Disk utilization
Date: Thu, 24 Sep 2009 18:09:48 +0900	[thread overview]
Message-ID: <87fxacbter.wl%jir@sekiba.com> (raw)
In-Reply-To: <1ee4eebe0909210654y3abe8bfaw14209035b0ebe625-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi, 

At Mon, 21 Sep 2009 16:54:50 +0300,
Saloustros Georgios wrote:

> Software Raid-0 consists of two Maxtor 500 GB with chuck size 64K.
> System's Memory is 2GB.
> For testing reasons I wrote a simple disk benchmark in java, where 8 threads
> append 256KB dummy blocks from memory to a log-file. Total IO is 8 GB.
> With ext3 mounted with data=writeback mode, each drive alone gives 63MB/sec
> and as a raid-0 array a total of 90 MB/sec.
> 
> Nilfs has worst performance for the same scenario. 1 Disk alone gives 34MB/sec
> and two disks on raid-0 setup 39 MB/sec.
> 
> Using iostat I can see that disks are 50% utilized with nilfs, whereas with
> ext3 are 100% utilized. Why is this happening? Is my configuration wrong? 

I'm not sure about the utilization but, the performance may be degraded
by the nilfs GC process.  As far as I see with my benchmark,  result is
twice better when stopping the GC process intentionally.

So if that's your case, performance will be expected as  38MB/sec for 1 disk
and 78MB/sec for raid-0.

Or you may tune your GC process by editing /etc/nilfs_cleanerd.conf,
decreasing nsegments_per_clean, increasing cleaning_interval.
Then GC process will affect the results less than it does.

Still, there is more room to improve write performance of nilfs2, I think :).

thanks

regards,
-- 
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>

      parent reply	other threads:[~2009-09-24  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 13:54 Low nilfs Disk utilization Saloustros Georgios
     [not found] ` <1ee4eebe0909210654y3abe8bfaw14209035b0ebe625-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-24  9:09   ` Jiro SEKIBA [this message]

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=87fxacbter.wl%jir@sekiba.com \
    --to=jir-hfpbi5wx9j54eiagz67ipq@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