From: David Masover <ninja@slaphack.com>
To: Craig Shelley <craig@microtron.org.uk>
Cc: reiserfs-list@namesys.com
Subject: Re: More Slowdown
Date: Tue, 15 Nov 2005 18:45:15 -0600 [thread overview]
Message-ID: <437A811B.5000509@slaphack.com> (raw)
In-Reply-To: <1132098269.7652.6.camel@teratron.lan.etheus.net>
Craig Shelley wrote:
> On Tue, 2005-11-15 at 15:13 -0800, Avuton Olrich wrote:
>
>>It's funny that you mention vim. vim seems to be what _really_ makes
>>my reiser4 do the 'slowdown'. I call it harddrive thrashing cause
>>that's what my wife calls it when she hears it from 5 yards away :)
>>Right before saving or saving/exiting it really does this thrashing,
>>Thank god you said this because I didn't think this 'slowdown' was the
>>same thing I was experiencing.
>
>
> This looks to be a similar thing with fsync(). It took approx 10 sec to
> save a file containing the string "Hello World"
> The results indicate that the time was spent in the fsync() call.
I got sick of waiting for it and nuked the fsync call. All my kernels
have a custom patch such that sys_fsync just returns true, no matter what.
Why?
Because vim shouldn't fsync, and neither should Evolution. It's been so
abused that I prefer to just manually run "sync" when I want something
flushed.
Even if fysnc was fast (only flushing the file that needed to flush),
that kind of abuse -- resizing a column -- kind of kills any advantage
of lazy writes.
next prev parent reply other threads:[~2005-11-16 0:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 22:22 More Slowdown Thorsten Hirsch
2005-11-15 22:55 ` Artur Makówka
2005-11-15 23:09 ` Andreas Rosander
2005-11-15 23:13 ` Avuton Olrich
2005-11-15 23:23 ` Artur Makówka
2005-11-15 23:44 ` Craig Shelley
2005-11-16 0:45 ` David Masover [this message]
2005-11-16 1:40 ` Francesco Biscani
2005-11-16 12:18 ` Nikita Danilov
2005-11-16 13:28 ` John Gilmore
2005-11-16 17:28 ` David Masover
2005-11-17 0:46 ` evilninja
2005-11-16 18:18 ` Artur Makówka
-- strict thread matches above, loose matches on Subject: below --
2005-11-17 13:47 Hesse, Christian
2005-11-22 10:23 ` Marcel Hilzinger
2005-11-22 10:38 ` Sander
2005-11-22 10:44 ` Marcel Hilzinger
2005-11-22 14:29 ` David Masover
2005-11-22 15:01 ` Marcel Hilzinger
2005-11-22 19:15 ` David Masover
2005-11-22 23:17 ` Hans Reiser
2005-11-22 15:08 ` Sander
2005-11-22 11:34 ` Ingo Bormuth
2005-11-22 12:29 ` Artur Makówka
2005-11-11 13:59 Slowdown is gone & apt-get works with updated reiser4. So nevermind John Gilmore
2005-11-12 3:07 ` michael chang
2005-11-12 6:38 ` Hans Reiser
2005-11-12 9:06 ` John Gilmore
2005-11-14 19:41 ` More Slowdown Craig Shelley
2005-11-14 19:53 ` jp
2005-11-14 20:47 ` Christian Iversen
2005-11-15 14:27 ` Craig Shelley
2005-11-15 18:04 ` Laurent Riffard
2005-11-15 18:42 ` Craig Shelley
[not found] ` <437AF653.9040001@namesys.com>
2005-11-16 9:33 ` Craig Shelley
2005-11-17 3:08 ` michael chang
2005-11-17 4:49 ` Hans Reiser
2005-11-17 12:02 ` Artur Makówka
2005-11-17 12:40 ` Vladimir V. Saveliev
2005-11-17 10:34 ` John Gilmore
2005-11-17 21:12 ` Hans Reiser
2005-11-18 20:45 ` Hans Reiser
2005-11-17 8:56 ` Ingo Bormuth
2005-11-17 9:36 ` PFC
2005-11-17 21:08 ` Hans Reiser
2005-11-19 4:44 ` michael chang
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=437A811B.5000509@slaphack.com \
--to=ninja@slaphack.com \
--cc=craig@microtron.org.uk \
--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.