public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: [OT] fast recursive local copy
Date: Sun, 16 Aug 2009 00:49:55 +0200	[thread overview]
Message-ID: <200908160049.55301.volkerarmin@googlemail.com> (raw)
In-Reply-To: <4a85cd72.QfZcpHnNyIPM7wHm%Joerg.Schilling@fokus.fraunhofer.de>

On Freitag 14 August 2009, Joerg Schilling wrote:
> Dirk Heinrichs <dirk.heinrichs@online.de> wrote:
> > Am Freitag 14 August 2009 10:50:45 schrieb Joerg Schilling:
> > > Note that on Linux you may need to add "-no-fsync" because file I/O is
> > > slow on Linux. On Solaris, not using -no-fsync slows things down by
> > > aprox. 10% but allows star to grant that everything was really copied
> > > to stable storage. On Linux, ot using -no-fsync slows things down by
> > > aprox. 400%, this is why I recommend to add "-no-fsync".
> >
> > This is also quite interesting. Do you have some (links to) recent
> > benchmarks which would second that? Could this even be depending on the
> > filesystem used on Linux?
>
> I did this test aprox. 3-4 years ago. You may try to do an own test and
> report.
>
> I did just rerun a test on a recent ubuntu in a VirtualBox environment and
> the speedup factor with -no-fsync was 8x.
>
> Jörg

reiser4 on raid5, compression is on, since no barriers, sync mode. Three runs, 
first without, second with, third without -no-fsync. echo 1 > 
/proc/sys/vm/drop_caches in between each run. temp was removed and recreated 
between each run. source and target on different md devices.

star: 0 blocks + 96006656 bytes (total of 96006656 bytes = 93756.50k).                         
star -copy -p -xdot -acl -sparse -C /usr/local/portage . temp/  0,85s user 
16,79s system 6% cpu 4:48,77 total 

star: 0 blocks + 96006656 bytes (total of 96006656 bytes = 93756.50k).
star -copy -p -xdot -acl -sparse -no-fsync -C /usr/local/portage . temp/  
0,43s user 3,14s system 24% cpu 14,389 total


star: 0 blocks + 96006656 bytes (total of 96006656 bytes = 93756.50k).
star -copy -p -xdot -acl -sparse -C /usr/local/portage . temp/  0,88s user 
15,93s system 6% cpu 4:13,76 total
  
but reiser4 is infamous for not loving fsync ;)



  parent reply	other threads:[~2009-08-15 22:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14  2:47 [gentoo-user] [OT] fast recursive local copy meino.cramer
2009-08-14  3:41 ` [gentoo-user] " Nikos Chantziaras
2009-08-14  8:30   ` Volker Armin Hemmann
2009-08-14  8:50   ` Joerg Schilling
2009-08-14 16:00     ` Dirk Heinrichs
2009-08-14 16:11       ` Joerg Schilling
2009-08-14 16:56         ` Dirk Heinrichs
2009-08-14 17:00     ` Dirk Heinrichs
2009-08-14 20:47       ` Joerg Schilling
2009-08-15 15:26         ` Dirk Heinrichs
2009-08-15 22:19           ` Volker Armin Hemmann
2009-08-15 22:49         ` Volker Armin Hemmann [this message]
2009-08-14  7:33 ` [gentoo-user] " Mike Kazantsev

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=200908160049.55301.volkerarmin@googlemail.com \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.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