mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shane <shane@zeke.yi.org>
To: linux-kernel@vger.kernel.org
Cc: lkml-frank@unternet.org
Subject: Re: severe slowdown with 2.4 series w/heavy disk access (revisited)
Date: 19 Apr 2002 19:07:29 -0400	[thread overview]
Message-ID: <1019257649.17679.45.camel@mars.goatskin.org> (raw)

Hi Frank,


>Hi'all,

>Anyone remember this thread:
>   "severe slowdown with 2.4 series w/heavy disk access"
>http://hypermail.spyroid.com/linux-kernel/archived/2001/week52/0266.html
>It describes the tendency of 2.4 series kernels to slowdown under I/O
>load. 

[..snip..]

I tried copying a 650MB file to the same file system on an IDE disk  
and...

(This is while the copy is running)

$ time ls -l
total 1284548
-rw-r--r--    1 shane    shane    685183312 Apr 19 18:13 650MB_tar_ball
-rw-r--r--    1 shane    shane    628895744 Apr 19 18:44 X
0.00user 0.00system 0:00.00elapsed 0%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (191major+35minor)pagefaults 0swaps
$ time ls -l
total 1287624
-rw-r--r--    1 shane    shane    685183312 Apr 19 18:13 650MB_tar_ball
-rw-r--r--    1 shane    shane    632041472 Apr 19 18:44 X
0.01user 0.00system 0:00.00elapsed 500%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (191major+35minor)pagefaults 0swaps
$ time ls -l
total 1290188
-rw-r--r--    1 shane    shane    685183312 Apr 19 18:13 650MB_tar_ball
-rw-r--r--    1 shane    shane    634662912 Apr 19 18:44 X
0.01user 0.00system 0:00.00elapsed 500%CPU (0avgtext+0avgdata 
0maxresident)k
0inputs+0outputs (191major+35minor)pagefaults 0swaps

vmstat 1 was running as well

   procs              memory      swap     io        system         cpu
 r w b  swpd   free     buf  cache si so bi bo   in    cs  us  sy  id
 0 0 0  53580  12296   3008 258120 0 0 0     0  180    87   0   0 100
 1 0 0  53580  12296   3008 258120 0 0 0     0  176    67   0   0 100
 3 0 0  53580 120492   3008 149836 0 0 2316  0  240   232   1  13  86
 2 0 0  53580  59432   3008 210596 0 0 30208 0  852  1491   3  42  55
 0 1 0  53580   4740   3012 264864 0 0 30212 0  652  1107   1  39  60
 0 1 1  53580   4600   3012 264696 0 0 23048 5760  586   885   2  31  67
 1 1 2  53580   4492   3016 264784 0 0 2560 17540  504   207   0   7  93
 0 1 1  53580   4324   3016 264944 0 0 2560 18304  501   256   0   6  94
 0 1 1  53580   4284   3016 264968 0 0 2048 16128  509   244   0   6  94
 0 1 1  53580   4488   3016 264740 0 0 2048 18020  499  206   0   5  95
 1 0 0  53604   4216   3028 266368 0 0 9732 10192  539   438   0  18  82
 0 1 1  53604   4424   3028 266056 0 0 6144 18148  525   395   2   6  92
 1 0 0  53604   3924   2904 266860 0 6019968 3900  614   866   0  35  65
 1 0 0  53604   4668   2908 265728 0 0 29188    0  634  1077   0  39  61
...

This is on a UP AMD Tbird, 384MB, on an IDE disk on a Promise TX133
controller. The Gnome desktop was responsive throughout the copy.

This is with the 2.4.19-pre6aa1 kernel. Give it a try...if you want.

Regards,

Shane


 


             reply	other threads:[~2002-04-19 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19 23:07 Shane [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-19 18:04 Frank de Lange
2002-04-19 17:35 Frank de Lange

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=1019257649.17679.45.camel@mars.goatskin.org \
    --to=shane@zeke.yi.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml-frank@unternet.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®