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 16:49:18 +0200 [thread overview]
Message-ID: <200405181649.22909.bernd-schubert@web.de> (raw)
In-Reply-To: <1084888676.20437.1477.camel@watt.suse.com>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2736 bytes --]
> > 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.
>
> Which procs contributed to this load? The simple dd should have kept
> the load at one.
Thats all I can see from top (2.4.26):
top - 16:45:14 up 4:47, 1 user, load average: 3.30, 2.80, 2.09
Tasks: 80 total, 1 running, 79 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0% user, 24.0% system, 0.0% nice, 76.0% idle
Mem: 3104428k total, 3018816k used, 85612k free, 228936k buffers
Swap: 1951888k total, 0k used, 1951888k free, 2662272k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1043 root 19 0 1392 364 320 D 40.7 0.0 3:11.55 dd
7 root 9 0 0 0 0 D 3.7 0.0 4:02.48 kupdated
6 root 9 0 0 0 0 D 1.7 0.0 2:15.18 bdflush
5 root 9 0 0 0 0 S 1.0 0.0 2:47.13 kswapd
17 root 9 0 0 0 0 D 0.3 0.0 0:46.62 kreiserfsd
1052 root 9 0 1040 1040 820 R 0.3 0.0 0:00.02 top
taylor:~# cat /proc/stat
cpu 402 0 538233 2938065
cpu0 221 0 267698 1470431
cpu1 181 0 270535 1467634
page 215506778 453499588
swap 1 0
intr 200179775 1738350 2 0 9 4 0 2 0 4 2 0 0 0 0 13 5 0 0 0 0 0 0 0 0 5017728
187006 0 0 0 193236650 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0
disk_io: (3,0):(4,4,32,0,0) (8,0):
(5058268,3638518,431013524,1419750,906999184)
ctxt 179608469
btime 1084874257
processes 1054
Unfortunality I even don't have an idea how to interprete those numbers.
> > Do you have any ideas how we could improve 2.4.x?
>
> 2.6.6-mm has a few key improvements. There's less metadata
> fragmentation thanks to some block allocator fixes. More importantly,
> during the rm, metadata blocks are read in 16 at a time instead of 1 at
> a time. I'd be happy to give someone pointers on porting the metadata
> readahead bits back to 2.4.
I certainly have neither the knowledge nor the time to do that.
Cheers,
Bernd
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-18 14:49 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
2004-05-18 13:57 ` Chris Mason
2004-05-18 14:49 ` Bernd Schubert [this message]
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=200405181649.22909.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.