Re: Horrible ftruncate performance

2003-07-17 Thread Dieter Nützel
Am Mittwoch, 16. Juli 2003 12:57 schrieb Oleg Drokin: > Hello! > > On Wed, Jul 16, 2003 at 12:47:53PM +0200, Dieter N?tzel wrote: > > > > Somewhat. > > > > Mouse movement is OK, now. But... > > > > 1+0 Records aus > > > > 0.000u 3.090s 0:16.81 18.3% 0+0k 0+0io 153pf+0w > > > > 0.000u 0.050s 0:0

Re: Horrible ftruncate performance

2003-07-16 Thread Oleg Drokin
Hello! On Wed, Jul 16, 2003 at 12:47:53PM +0200, Dieter N?tzel wrote: > > > Somewhat. > > > Mouse movement is OK, now. But... > > > 1+0 Records aus > > > 0.000u 3.090s 0:16.81 18.3% 0+0k 0+0io 153pf+0w > > > 0.000u 0.050s 0:00.27 18.5% 0+0k 0+0io 122pf+0w > > > INSTALL/SOURCE> time dd if=/

Re: Horrible ftruncate performance

2003-07-16 Thread Dieter Nützel
Am Mittwoch, 16. Juli 2003 12:35 schrieb Oleg Drokin: > Hello! > > On Tue, Jul 15, 2003 at 09:55:09PM +0200, Dieter N?tzel wrote: > > Somewhat. > > Mouse movement is OK, now. But... > > > > 1+0 Records aus > > 0.000u 3.090s 0:16.81 18.3% 0+0k 0+0io 153pf+0w > > 0.000u 0.050s 0:00.27 18.5% 0

Re: Horrible ftruncate performance

2003-07-16 Thread Oleg Drokin
Hello! On Tue, Jul 15, 2003 at 09:55:09PM +0200, Dieter N?tzel wrote: > Somewhat. > Mouse movement is OK, now. But... > > 1+0 Records aus > 0.000u 3.090s 0:16.81 18.3% 0+0k 0+0io 153pf+0w > 0.000u 0.050s 0:00.27 18.5% 0+0k 0+0io 122pf+0w > INSTALL/SOURCE> time dd if=/dev/zero of=sparse1

Re: Horrible ftruncate performance

2003-07-15 Thread Dieter Nützel
Am Dienstag, 15. Juli 2003 19:05 schrieb Oleg Drokin: > Hello! > > On Tue, Jul 15, 2003 at 06:48:58PM +0200, Dieter N?tzel wrote: > > ! > >! The 'right' questions are: > > * Are the 204,804 MB really needed? > >

Re: Horrible ftruncate performance

2003-07-11 Thread Szakacsits Szabolcs
On Sat, 12 Jul 2003, Carl-Daniel Hailfinger wrote: > Szakacsits Szabolcs wrote: > > On Fri, 11 Jul 2003, Dieter [iso-8859-1] Nützel wrote: > > > >>More than 506 times... > >>=> 506.34 seconds (8:26.34) / 0.01 seconds = 50.634 times ;-))) > > > > I guess you mean 50,634 or 50634 times faster? But I

Re: Horrible ftruncate performance

2003-07-11 Thread Carl-Daniel Hailfinger
Szakacsits Szabolcs wrote: > On Fri, 11 Jul 2003, Dieter [iso-8859-1] Nützel wrote: > >>More than 506 times... >>=> 506.34 seconds (8:26.34) / 0.01 seconds = 50.634 times ;-))) > > I guess you mean 50,634 or 50634 times faster? But I'm afraid you didn't > test what you should have. Interestingly,

Re: Horrible ftruncate performance

2003-07-11 Thread Szakacsits Szabolcs
On Fri, 11 Jul 2003, Dieter [iso-8859-1] Nützel wrote: > As reminder the old numbers (single U160, IBM 10k rpm): For the below test, disk doesn't really matter. It's almost [should be (*)] pure CPU job. Otherwise I'd have suggested a 'sync' at the end(**). > 2.4.21-jam1 (aa1) plus all data-logg

Re: Horrible ftruncate performance

2003-07-11 Thread Dieter Nützel
Am Freitag, 11. Juli 2003 20:32 schrieb Chris Mason: > On Fri, 2003-07-11 at 13:27, Dieter Nützel wrote: > > > 2.5 porting work has restarted at last, Oleg's really been helpful with > > > keeping the 2.4 stuff up to date. > > > > Nice but. > > > > Patches against latest -aa could be helpful, then.

Re: Horrible ftruncate performance

2003-07-11 Thread Philippe Gramoullé
Hello Dieter, Before we used to host web files so reiserfs + quota was mandatory. We could live without the data-logging code. Now that we use reiserfs for fsync intensive applications, data-logging + quota + latest IO improvements from Chris that were committed recently in 2.4.22-pre and it w

Re: Horrible ftruncate performance

2003-07-11 Thread Chris Mason
On Fri, 2003-07-11 at 13:27, Dieter Nützel wrote: > > 2.5 porting work has restarted at last, Oleg's really been helpful with > > keeping the 2.4 stuff up to date. > > Nice but. > > Patches against latest -aa could be helpful, then. Hmmm, the latest -aa isn't all that latest right now. Do you

Re: Horrible ftruncate performance

2003-07-11 Thread Dieter Nützel
Am Freitag, 11. Juli 2003 19:09 schrieb Chris Mason: > On Fri, 2003-07-11 at 11:44, Oleg Drokin wrote: > > Hello! > > > > On Fri, Jul 11, 2003 at 05:34:12PM +0200, Marc-Christian Petersen wrote: > > > > Actually I did it already, as data-logging patches can be applied to > > > > 2.4.22-pre3 (where

Re: Horrible ftruncate performance

2003-07-11 Thread Chris Mason
On Fri, 2003-07-11 at 11:44, Oleg Drokin wrote: > Hello! > > On Fri, Jul 11, 2003 at 05:34:12PM +0200, Marc-Christian Petersen wrote: > > > > Actually I did it already, as data-logging patches can be applied to > > > 2.4.22-pre3 (where this truncate patch was included). > > > > Maybe it _IS_ time

Re: Horrible ftruncate performance

2003-07-11 Thread Oleg Drokin
Hello! On Fri, Jul 11, 2003 at 05:34:12PM +0200, Marc-Christian Petersen wrote: > > Actually I did it already, as data-logging patches can be applied to > > 2.4.22-pre3 (where this truncate patch was included). > > > Maybe it _IS_ time for this _AND_ all the other data-logging patches? > > > 2.4.

Re: Horrible ftruncate performance

2003-07-11 Thread Oleg Drokin
Gello! On Fri, Jul 11, 2003 at 05:32:49PM +0200, Dieter N?tzel wrote: > > > OK some "hand work"... > Where comes this from? It was there for a lot of time. Like for not less than 2 years, I'd say. > I don't find it my tree: reiserfs quota patch got rid of it. Here's relevant part of my diff:

Re: Horrible ftruncate performance

2003-07-11 Thread Dieter Nützel
Am Freitag, 11. Juli 2003 17:36 schrieb Marc-Christian Petersen: > On Friday 11 July 2003 17:32, Dieter Nützel wrote: > > Hi Dieter, > > > Where comes this from? > > I don't find it my tree: > > > > fs/eiserfs/inode.c > > > > -if (un.unfm_nodenum) > > inode->i_blocks +=

Re: Horrible ftruncate performance

2003-07-11 Thread Dieter Nützel
Am Freitag, 11. Juli 2003 17:32 schrieb Oleg Drokin: > Hello! > > On Fri, Jul 11, 2003 at 05:27:25PM +0200, Dieter N?tzel wrote: > > > Actually I did it already, as data-logging patches can be applied to > > > 2.4.22-pre3 (where this truncate patch was included). > > > > No -aaX. > > Right. > > > >

Re: Horrible ftruncate performance

2003-07-11 Thread Marc-Christian Petersen
On Friday 11 July 2003 17:32, Dieter Nützel wrote: Hi Dieter, > Where comes this from? > I don't find it my tree: > > fs/eiserfs/inode.c > > -if (un.unfm_nodenum) > inode->i_blocks += inode->i_sb->s_blocksize / 512; > //mark_tail_converted (inode); reise

Re: Horrible ftruncate performance

2003-07-11 Thread Marc-Christian Petersen
On Friday 11 July 2003 17:24, Oleg Drokin wrote: Hi Oleg, > Actually I did it already, as data-logging patches can be applied to > 2.4.22-pre3 (where this truncate patch was included). > > Maybe it _IS_ time for this _AND_ all the other data-logging patches? > > 2.4.22-pre5? > It's Chris turn. I

Re: Horrible ftruncate performance

2003-07-11 Thread Dieter Nützel
Am Freitag, 11. Juli 2003 17:24 schrieb Oleg Drokin: > Hello! > > On Fri, Jul 11, 2003 at 05:16:56PM +0200, Dieter N?tzel wrote: > > OK some "hand work"... Where comes this from? I don't find it my tree: fs/eiserfs/inode.c -if (un.unfm_nodenum) inode->i_blocks += ino

Re: Horrible ftruncate performance

2003-07-11 Thread Oleg Drokin
Hello! On Fri, Jul 11, 2003 at 05:27:25PM +0200, Dieter N?tzel wrote: > > Actually I did it already, as data-logging patches can be applied to > > 2.4.22-pre3 (where this truncate patch was included). > No -aaX. Right. > > > Maybe it _IS_ time for this _AND_ all the other data-logging patches? >

Re: Horrible ftruncate performance

2003-07-11 Thread Dieter Nützel
Am Freitag, 11. Juli 2003 17:24 schrieb Oleg Drokin: > Hello! > > On Fri, Jul 11, 2003 at 05:16:56PM +0200, Dieter N?tzel wrote: > > OK some "hand work"... > > Actually I did it already, as data-logging patches can be applied to > 2.4.22-pre3 (where this truncate patch was included). No -aaX. > >