From: Eric Whiting <ewhiting@amis.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrea Arcangeli <andrea@suse.de>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: -mmX 4G patches feedback [numbers: how much performance impact]
Date: Tue, 06 Apr 2004 08:49:21 -0600 [thread overview]
Message-ID: <4072C371.CFA9CA1E@amis.com> (raw)
In-Reply-To: 20040406115539.GA31465@elte.hu
Ingo Molnar wrote:
>
> [***] non-PAE 4:4 kernels are being used too - there are a fair number
> of users who run simulation code using 4GB of physical RAM and a
> pure 4:4 kernel with no highmem features required. For these 4:4
> users the overhead on number-crunching is even smaller, only
> 0.03%.
Ingo,
What you describe above is a situation that matches our environment.
We do have servers with more than 4G RAM that need PAE, but we have more
workstations with 4G (or 3G) of RAM that do not need PAE, but do need the 4:4
VM. In terms of a large simulation (> 3G of userspace VM) running to completion
-- a 3G RAM box with 4:4 VM is better than a 32G box with 3:1 VM -- even though
the box with 3G RAM may swap a little/lot.
4:4 is not the 'real' long term solution, but it will let us run more jobs on
32bit hardware until the x86_64 HW/SW support stabilizes a little more. We
currently run jobs on solaris when single process VM requirement exceeds 4G.
eric
next prev parent reply other threads:[~2004-04-06 20:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 16:36 -mmX 4G patches feedback Eric Whiting
2004-04-05 17:46 ` Andrea Arcangeli
2004-04-05 21:35 ` Eric Whiting
2004-04-05 22:16 ` Andrea Arcangeli
2004-04-06 11:55 ` -mmX 4G patches feedback [numbers: how much performance impact] Ingo Molnar
2004-04-06 14:49 ` Eric Whiting [this message]
2004-04-06 15:59 ` Andrea Arcangeli
2004-04-06 16:13 ` Arjan van de Ven
2004-04-06 16:39 ` Andrea Arcangeli
2004-04-06 17:24 ` Ingo Molnar
2004-04-06 17:57 ` Andrea Arcangeli
2004-04-07 22:54 ` Martin J. Bligh
2004-04-07 22:50 ` Andrea Arcangeli
2004-04-06 19:25 ` Ingo Molnar
2004-04-06 20:25 ` Andrea Arcangeli
2004-04-07 6:03 ` Andrea Arcangeli
2004-04-07 6:46 ` Ingo Molnar
2004-04-07 7:23 ` Andrea Arcangeli
2004-04-07 8:23 ` Ingo Molnar
2004-04-07 21:35 ` Andrea Arcangeli
2004-04-07 17:27 ` Andrea Arcangeli
2004-04-07 7:25 ` Ingo Molnar
2004-04-07 21:39 ` Andrea Arcangeli
2004-04-07 22:58 ` Martin J. Bligh
2004-04-07 23:01 ` Andrea Arcangeli
2004-04-07 23:21 ` Martin J. Bligh
2004-04-07 23:18 ` Andrea Arcangeli
2004-04-07 23:34 ` Martin J. Bligh
2004-04-08 0:18 ` Andrea Arcangeli
2004-04-08 6:24 ` Martin J. Bligh
2004-04-08 21:59 ` Andrea Arcangeli
2004-04-08 22:19 ` Martin J. Bligh
2004-04-08 22:19 ` Andrea Arcangeli
2004-04-08 23:14 ` Martin J. Bligh
2004-04-08 23:22 ` Andrea Arcangeli
2004-04-08 23:42 ` Martin J. Bligh
2004-04-08 23:49 ` Andrea Arcangeli
2004-04-07 21:19 ` -mmX 4G patches feedback Martin J. Bligh
2004-04-07 21:49 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2004-04-06 17:59 -mmX 4G patches feedback [numbers: how much performance impact] Manfred Spraul
2004-04-06 18:41 ` Andrea Arcangeli
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=4072C371.CFA9CA1E@amis.com \
--to=ewhiting@amis.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zaitcev@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.