All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: Chris Mason <mason@suse.com>
Cc: Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: large files
Date: Tue, 18 May 2004 15:42:06 +0200	[thread overview]
Message-ID: <200405181544.36152.bernd-schubert@web.de> (raw)
In-Reply-To: <1084824741.20437.368.camel@watt.suse.com>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1963 bytes --]

Hello Chris,

>
> As a comparison data point, could you please try 2.6.6-mm3?  I realize
> you don't want to run this kernel in production, but it would tell us if
> I understand the problems at hand.

the results in 2.6.6-mm3 are below, we almost consider to run this kernel 
version.

Here are two other interesting facts:

1.) During the filecreation in 2.4.26 the load on the system was around 3-4, 
whereas in 2.6.6-mm3 the load was at about 8-9.

2.) When the dd file creation process finished (2.4.26 was running) the system 
became so unresponsible, that the drdb connection timed out and a resync 
process automatically started when the system became responsible again. I 
don't have any comparism to 2.6.6-mm3 since we would need another drbd 
version. Also, I don't know if this happend when dd finished or when 
rm-started, since both were running from a script.

Here are the measured times for file creation and file deleting

=====> 2.4.26:

taylor:~# cat test.out-2.4.26
time dd if=/dev/zero of=/worka/testfile.dd bs=1M count=300000
300000+0 records in
300000+0 records out
314572800000 bytes transferred in 5746.266841 seconds (54743855 bytes/sec)

real	95m46.275s
user	0m0.760s
sys	29m57.800s


time rm -fr /worka/testfile.dd

real	11m20.589s
user	0m0.000s
sys	4m59.850s


=====> 2.6.6-mm3


taylor:~# cat test.out-2.6.6-mm3
time dd if=/dev/zero of=/worka/testfile.dd bs=1M count=300000
300000+0 records in
300000+0 records out
314572800000 bytes transferred in 4902.873869 seconds (64160900 bytes/sec)

real	81m46.211s
user	0m1.172s
sys	22m26.010s


time rm -fr /worka/testfile.dd

real	1m38.000s
user	0m0.000s
sys	1m5.872s



Do you have any ideas how we could improve 2.4.x? 


Thanks,
	Bernd


-- 
Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
e-mail: bernd.schubert@pci.uni-heidelberg.de

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-05-18 13:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 19:48 large files Bernd Schubert
2004-05-17 20:12 ` Chris Mason
2004-05-17 20:25   ` Bernd Schubert
2004-05-18 13:42   ` Bernd Schubert [this message]
2004-05-18 13:57     ` Chris Mason
2004-05-18 14:49       ` Bernd Schubert
2004-05-18 15:07         ` Chris Mason
2004-05-18 15:19           ` Hans Reiser
2004-05-18 15:40             ` Chris Mason
  -- strict thread matches above, loose matches on Subject: below --
2003-06-10 22:38 Large files Ray Lee
2003-06-10 13:57 Richard B. Johnson
2003-06-10 14:16 ` ZCane, Ed (Test Purposes)
2003-06-10 14:17 ` Matti Aarnio
2003-06-10 15:12   ` Richard B. Johnson
2003-06-10 17:25     ` Martin Mares
2003-06-10 18:14     ` Andreas Dilger
2003-06-10 22:12     ` Rob Landley
2003-06-10 20:14 ` David Schwartz
2003-06-10 20:31   ` Richard B. Johnson

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=200405181544.36152.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=Reiserfs-List@namesys.com \
    --cc=mason@suse.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.