public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Satoshi Oshima <oshima@sdl.hitachi.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IA64 Linux VM performance woes
Date: Wed, 21 Apr 2004 18:00:42 -0300	[thread overview]
Message-ID: <20040421210042.GD16891@logos.cnet> (raw)
In-Reply-To: <JT20040421213923.40329203@sdl.hitachi.co.jp>

On Wed, Apr 21, 2004 at 09:39:23PM +0900, Satoshi Oshima wrote:
> Hello, Michael and all.
> 
> We have realized the same kind of performance issue. 
> In our case it is not an IA64 huge scale system but an IA32
> server system.
> 
> In our experiment, we see file I/O throughput decline on 
> the server with over 8GByte memory. Kernel versions we use 
> are 2.6.0 and Red Hat AS3. We show our experiment.
> 
> Below is our hardware configuration and test bench.
> 
> CPUs: Xeon 1.6Ghz - 4way
> Memory: 12GB
> Storage: ATA 120GB
> File I/O workload generator consists of 1024 processes and 
> generates 100KByte to 5MByte file write. Using "mem=" option, 
> we change the memory recognition 2GByte to 12GB.
> 
> Below is the result ( unit: MByte/sec).
> 
>       2GB  4GB  8GB  12GB
> 2.6.0 13.1 18.5 18.4 16.1
> AS3   11.0 11.3 10.3 8.92
> 
> The result shows throughput decline occurs when the server 
> has over 8GByte memory.

Can you share the tests with us? It would be great. 

> We agree that your proposal is good idea. It reduces cache 
> memory reclaiming cost to set upper bound on number of 
> cache memory pages. 

I'm not exactly sure of the problem (others (Andrea, Andrew, etc) probably are). Still,
one useful thing would be to rerun the benchmarks on recent kernels (2.6.6-rc2, which contains a 
lot of VM rewrite and tuning). It will be interesting to know the results.

> Generally it is very difficult to build one system which 
> could handle various type of workloads well. So we hope 
> Linux would have kernel parameter tuning interface.
> 
> We would be very happy if we could share information to 
> manage large scale memory.

  reply	other threads:[~2004-04-21 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 12:39 IA64 Linux VM performance woes Satoshi Oshima
2004-04-21 21:00 ` Marcelo Tosatti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-13 18:53 Michael E. Thomadakis

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=20040421210042.GD16891@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oshima@sdl.hitachi.co.jp \
    /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