From: Dirk Schenkewitz <Dirk.Schenkewitz@interface-ag.com>
To: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: Corrupted/unreadable journal: reiser vs. ext3
Date: Wed, 12 Feb 2003 11:48:14 +0100 [thread overview]
Message-ID: <3E4A266E.2A258472@interface-ag.com> (raw)
In-Reply-To: 93F527C91A6ED411AFE10050040665D0049C06D5@corpusmx1.us.dg.com
Wayne,
berthiaume_wayne@emc.com schrieb:
>
> Dirk, I'd be interested in hearing from you your performance
> experience with ext3 when it reaches 96% full.
Well (*shrug*), there seems to be nothing special about it. I did
not do any timing test when such a fileysytem went full. In fact,
becoming 100% full is not "mormal", it happens when I put stuff
on it just to have it out of the way for some time. The filesystem
is then used as some kind of "storage cellar".
Aside from that - speed becomes noticeable (I believe, at least)
when using 'xv' on a directory with lots of pictures, say, between
2000 and 3000, and the thumbnails are loaded during the first access.
This takes more than a minute (estimated, I did not look at the
clock).
Another thing is when 'xv' creates the thumbnails. A few times it
happened that a filesystem which was rather full ran out of space
when creating the thumbnails. (That's not critical, all you "loose"
are some of the thumbnails, which can be recreated any time later.)
But I don't know how/when 'xv' stores the thumbnails, I only know
that they are kept in memory as long as they are in use. Then linux
itself does some buffering, so only the first access on a directory
can make a testimony. That said, I can can only talk of my subjec-
tive impressions, and I have not noticed any slowdown until there
are 0 bytes left. But it is hard to tell, because the difference
between 96% and 100% are only 320 MB on a 8 GB partition, and that
space fills up rather fast.
While you ask - what are the "amounts" of slowdown if a reiserfs
gets more than 96% full?
- Less than 4% percent? (I might not notice that.)
- between 4% and 8%? (I might notice, but I can live with that
easily. Then again, ext3 doesn't seem to have such problems.)
- more than 8%, maybe much more? (That might become annoying.
In that case I believe that ext3 is better for my purposes.)
You see, I'm not an expert, I'm "just using filesystems". Please
take the mentioned percentages as guesses - depending on the
situation, I might not even notice 10% slowdown...
Hope that answers your question - does it?
Happy coding
dirk
--
Dirk Schenkewitz
InterFace AG fon: +49 (0)89 / 610 49 - 126
Leipziger Str. 16 fax: +49 (0)89 / 610 49 - 83
D-82008 Unterhaching
http://www.interface-ag.de mailto:dirk.schenkewitz@interface-ag.de
next prev parent reply other threads:[~2003-02-12 10:48 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 19:43 Corrupted/unreadable journal: reiser vs. ext3 berthiaume_wayne
2003-02-12 10:48 ` Dirk Schenkewitz [this message]
2003-02-12 10:59 ` Hans Reiser
2003-02-12 11:24 ` Frank Baumgart
2003-02-12 11:35 ` Stefan Traby
2003-02-12 11:54 ` Dirk Schenkewitz
2003-02-12 12:42 ` Hans Reiser
2003-02-12 13:25 ` Dirk Schenkewitz
2003-02-12 16:22 ` Sam Vilain
2003-02-12 16:53 ` Anders Widman
2003-02-12 17:19 ` Hans Reiser
2003-02-12 17:40 ` Anders Widman
2003-02-12 18:15 ` Dirk Mueller
2003-02-12 18:20 ` Anders Widman
2003-02-12 18:20 ` Chris Dukes
2003-02-13 20:08 ` Zygo Blaxell
-- strict thread matches above, loose matches on Subject: below --
2003-02-20 9:55 Dirk Schenkewitz
2003-02-20 10:20 ` Anders Widman
2003-02-17 10:04 Dirk Schenkewitz
2003-02-20 1:27 ` Juan Quintela
2003-02-20 9:03 ` Anders Widman
2003-02-14 14:30 Dirk Schenkewitz
2003-02-14 14:20 Dirk Schenkewitz
2003-02-14 20:58 ` Valdis.Kletnieks
2003-02-14 0:18 Sam Vilain
2003-02-23 23:31 ` Zygo Blaxell
2003-02-24 1:14 ` Anders Widman
2003-02-14 0:17 Sam Vilain
2003-02-14 0:16 Sam Vilain
2003-02-23 23:10 ` Zygo Blaxell
2003-02-12 20:57 Dirk Schenkewitz
2003-02-12 20:05 Dirk Schenkewitz
2003-02-13 22:49 ` Zygo Blaxell
2003-02-14 0:32 ` Hans Reiser
2003-02-14 8:18 ` Oleg Drokin
2003-02-14 10:13 ` Andreas Dilger
2003-02-14 10:17 ` Oleg Drokin
2003-02-14 10:50 ` Andreas Dilger
2003-02-14 10:59 ` Oleg Drokin
2003-02-14 13:34 ` Hans Reiser
2003-02-14 16:04 ` Rudy Zijlstra
2003-02-14 19:06 ` Andreas Dilger
2003-02-14 19:19 ` Hans Reiser
2003-02-15 12:51 ` Vitaly Fertman
2003-02-15 13:00 ` Vitaly Fertman
2003-02-18 19:50 ` Hans Reiser
2003-02-18 20:05 ` Vitaly Fertman
2003-02-18 22:18 ` Hans Reiser
2003-02-15 13:04 ` Anders Widman
2003-02-15 13:23 ` Oleg Drokin
2003-02-17 19:43 ` Hans Reiser
2003-02-15 22:37 ` Andreas Dilger
2003-02-18 18:21 ` Hans Reiser
2003-02-18 19:22 ` Oleg Drokin
2003-02-18 19:28 ` Hans Reiser
2003-02-18 21:17 ` Valdis.Kletnieks
2003-02-18 22:02 ` Matthias Andree
2003-02-19 6:26 ` Oleg Drokin
2003-02-18 22:23 ` Hans Reiser
2003-02-12 18:27 Anders Widman
2003-02-11 18:59 Dirk Schenkewitz
2003-02-11 20:27 ` Hans Reiser
2003-02-11 21:30 ` Mike Hodson
2003-02-11 21:47 ` Hans Reiser
2003-02-11 21:58 ` Hans Reiser
2003-02-12 6:35 ` Oleg Drokin
2003-02-11 23:11 ` Adam Goryachev
2003-02-11 23:17 ` Anders Widman
2003-02-12 0:12 ` Hans Reiser
2003-02-12 10:23 ` Anders Widman
2003-02-12 10:47 ` Hans Reiser
2003-02-12 11:12 ` Adam Goryachev
2003-02-12 13:42 ` Anders Widman
2003-02-12 14:15 ` Russell Coker
2003-02-12 15:26 ` Anders Widman
2003-02-12 16:22 ` bscott
2003-02-12 16:28 ` Russell Coker
2003-02-12 16:40 ` Anders Widman
2003-02-13 3:42 ` Zygo Blaxell
2003-02-13 10:13 ` Anders Widman
2003-02-13 14:44 ` Rudy Zijlstra
2003-02-13 3:31 ` Zygo Blaxell
2003-02-12 16:39 ` Sam Vilain
2003-02-12 5:12 ` Ross Vandegrift
2003-02-12 7:17 ` Oleg Drokin
2003-02-12 10:17 ` Alexander Lyamin
2003-02-12 10:19 ` Alexander Lyamin
2003-02-12 16:25 ` Vitaly Fertman
2003-02-12 16:56 ` Anders Widman
2003-02-12 17:13 ` Oleg Drokin
2003-02-12 1:02 ` Mike Hodson
2003-02-12 7:25 ` Oleg Drokin
2003-02-12 9:45 ` Hans Reiser
2003-02-12 16:09 ` Sam Vilain
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=3E4A266E.2A258472@interface-ag.com \
--to=dirk.schenkewitz@interface-ag.com \
--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.