From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Bormuth Subject: Re: More Slowdown Date: Thu, 17 Nov 2005 09:56:44 +0100 Message-ID: <20051117085644.GA23183@kruemel> References: <200511111359.39715.jgilmore@glycou.com> <200511120906.39109.jgilmore@glycou.com> <1131997263.10816.56.camel@teratron.lan.etheus.net> <200511142147.07787.chrivers@iversen-net.dk> <1132064829.8002.9.camel@teratron.lan.etheus.net> Reply-To: Ingo Bormuth Mime-Version: 1.0 Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com Content-Disposition: inline In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: reiserfs-list@namesys.com Cc: ingo@bormuth.org If you are frequently hit by fsync (as some of the previosly posters told us) an option might be to say something as tmgr.atom_max_age=30 (or tmgr.atom_max_size=?) in fstab (or remount the drive in vulnerable situations). Of course that sacrifices large parts of reiser4's mean performance, but that might be better than a largely unusable machine. One day reiser4 will be fully optimized. On 2005-11-16 22:08, michael chang wrote: > That would explain any > jerkiness -- it's because Reiser4 is writing everything from the last > real write to the actual disk to now (the current real right) in one > go, and making everything wait. -- Ingo Bormuth, voicebox & telefax: +49-12125-10226517 '(~o-o~)' public key 86326EC9, http://ibormuth.efil.de/contact ---ooO--(.)--Ooo---