mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: linux-kernel@vger.kernel.org
Cc: andrea@suse.de
Subject: Write throughput in >= 2.4.10
Date: 18 Oct 2001 21:13:13 +0200	[thread overview]
Message-ID: <87669c92ye.fsf@atlas.iskon.hr> (raw)

It looks like recent kernels have some serious trouble during simple
writing of files. Throughput is cut to half.

2.4.12-ac3 (Riel VM):

   procs                      memory    swap          io     system         cpu
 r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
 0  4  1      0   2548   7652 369104   0   0     0 21992  291   592   0  23  77
 0  4  1      0   2556   7652 369104   0   0     0 22500  280   175   0   3  97
 0  4  1      0   3064   7652 368588   0   0     8 19644  278   202   0   4  96
...

2.4.13-pre4 (Andrea/Linus VM):

   procs                      memory    swap          io     system         cpu
 r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
 1  1  1  30312   2884   2304 384076   0  28     0  7784  199   241   0  12  88
 0  1  1  30316   2068   2256 385772   0 132     4  7900  186   188   1   8  91
 0  1  0  30316   3960   2232 384140   0   0     8  6744  179   204   0   4  96
...

'bo' column is the one to check out... I copied just 3 lines, but they
are all alike. 2.4.13-pre ends up with 11MB/sec, where -ac kernels are
over 20MB/sec (during sequential writing of big files - ext2 of course).

Also it looks like pre4 swaps when it is not necessary to do so. With
380MB in page cache I don't expect any swap traffic at all.
-- 
Zlatko

             reply	other threads:[~2001-10-18 20:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 19:13 Zlatko Calusic [this message]
2001-10-18 19:36 ` Marcelo Tosatti
2001-10-18 21:26   ` Zlatko Calusic

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=87669c92ye.fsf@atlas.iskon.hr \
    --to=zlatko.calusic@iskon.hr \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.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®