From: Hans K. R. <hk...@is...> - 2004-09-10 21:58:59
|
On Thu, 2004-09-09 at 04:22, Peter Cordes wrote: > On Wed, Sep 08, 2004 at 01:03:40PM +0200, Hans Kristian Rosbach wrote: > > On Wed, 2004-09-08 at 12:46, Vincent Hanquez wrote: > > > on 2.4.24-om1 it could be possible, without the fix, to corrupt memory. > > > you have to run a newer kernel to be sure that's not related to that. > > > > Okay, I hope it's fixed too.. > > > > I haven't rebooted yet, so further info follows: > > > > But, now that I try to run 'tar jxvf gcc.tar.bz2' it seems so annoyingly > > slow that I after a while checked top.. It uses ~5% cpu.. > > tar is? That sounds about right. Most of the work in extracting a tarball > is bzip2 decompression. bzip2 is an expensive algorithm. You should see > that bzip2 is using most of the CPU, with tar taking a little, and some > system time as the kernel takes time to find disk blocks to put all that > stuff. > > If bzip2 is only getting 5%, that would be a problem. Okay, total cpu usage was 5%. Tar, bzip2 and X included. -HK |