From: Oleg Drokin <green@namesys.com>
To: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Cc: Andrea Arcangeli <andrea@suse.de>, reiserfs-list@namesys.com
Subject: Re: Copy time comparison 2.4.20-pre6 <-> 2.4.19+data-logging (was:Compatibility of current 2.4.19.pending ...)
Date: Tue, 17 Sep 2002 10:33:21 +0400 [thread overview]
Message-ID: <20020917103321.C25766@namesys.com> (raw)
In-Reply-To: <3D867C14.5060404@mb.tu-ilmenau.de>
Hello!
On Tue, Sep 17, 2002 at 02:49:24AM +0200, Manuel Krause wrote:
> >What tool do you use for backup?
> Hey, Oleg, you should know this; I stayed with my simple but useful
> scripts using "cp -ax A/. B/" for testing reiserfs performance on this
> command related to my reiserfs partitions' content. That content is not
I am just making sure.
> >Also very huge difference is seen when creating holes ;)
> >e.g compare time of seeking to 128Gb and writing one byte between
> >2.4.20-pre7 and 2.4.20-pre6 ;)
> >Code for that was once posted on our mailing list.
> >When you will feel that 2.4.20-pre7 hanged, don't trust that feeling
> >and wait till the end of operation. ;)
> You're kind of joking?! "time <command>" should show the total lack of
> time related performance, when [throughput] is divided by [time] or
I must be missing something, but why do you want to divide throughput by time?
throughput is amount of data divided by time.
> not?! I calculated these values manually based upon the timings & df
> values after copying. Yes, I want to show my personal engagement for the
> reiserfs community, too.
Hm. Are you sure you are hitting write-speed limit?
May be you are read-speed bounded? Can you please check that?
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2002-09-17 6:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 0:24 Compatibility of current 2.4.19.pending patchset with old data-logging?? Manuel Krause
2002-09-12 13:28 ` newbie how to darren
2002-09-12 14:37 ` Hans Reiser
2002-09-12 15:12 ` Guillermo Torreiro
2002-09-12 21:30 ` Copy time comparison 2.4.20-pre6 <-> 2.4.19+data-logging (was:Compatibility of current 2.4.19.pending ...) Manuel Krause
2002-09-13 7:37 ` Oleg Drokin
2002-09-13 23:07 ` Manuel Krause
2002-09-14 9:02 ` Oleg Drokin
2002-09-17 0:53 ` Manuel Krause
[not found] ` <3D867C14.5060404@mb.tu-ilmenau.de>
2002-09-17 6:33 ` Oleg Drokin [this message]
2002-09-17 13:56 ` Manuel Krause
2002-09-17 14:00 ` Oleg Drokin
2002-09-17 17:39 ` Manuel Krause
2002-09-18 5:20 ` Oleg Drokin
2002-09-19 1:14 ` Manuel Krause
2002-09-19 6:34 ` Oleg Drokin
2002-09-19 15:52 ` Manuel Krause
2002-09-19 16:01 ` Oleg Drokin
2002-09-23 0:36 ` Manuel Krause
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=20020917103321.C25766@namesys.com \
--to=green@namesys.com \
--cc=andrea@suse.de \
--cc=manuel.krause@mb.tu-ilmenau.de \
--cc=reiserfs-list@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.