thanks for you help. i tracked down the problem to very poor
configuration of my hard drive. hdparm revealed buffered disk read speed
of 2.5 MB/ sec. Tuning the drive using hdparm, I got the speed up
to 27 MB / sec. Now the same tar task runs much faster and kjournald
uses very little cpu time.
ma
This probably should not matter, but, was this after extensive system
resource using tasks (i.e. did you do anything big before hand). Try
tarring a similar group of files again right after booting, and tell
me how long it takes
No other task running at the time (besides sleeping processes). The
tar-ing took about 25 minutes.
Martin
Leonid Grinberg ([EMAIL PROTECTED]) wrote:
> I don't think that's right... are you doing anything else at the time?
> How long did the tar-ing take?
--
Linux is user friendly. It's just ve
I don't think that's right... are you doing anything else at the time?
How long did the tar-ing take?
Is it normal to have kjournal average 45% CPU usage (nice = 0) when I
tar (without compression) a folder with 2GB of standard mp3 files on an
ordinary pentium 4, 512mb ram, dell box? I'm not too familiar with the workings
of the EXT3 filesystem, but those values seemed a bit suspect.
thanks,
ma
5 matches
Mail list logo
