public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Largest mallocs opteron vs. 32bit systems
@ 2004-04-27  6:24 Soeren Sonnenburg
  2004-04-28  6:06 ` Soeren Sonnenburg
  0 siblings, 1 reply; 2+ messages in thread
From: Soeren Sonnenburg @ 2004-04-27  6:24 UTC (permalink / raw)
  To: Linux Kernel

Hello...

I just did some tests trying to malloc() memory on an opteron and a xeon
system...

I wonder why I see regression for the opteron in 32bit mode. Comments
welcome (workarounds even more). Anyhow my observations:

malloc large block:

opteron -> up to 7G (64bit exe) -> up to 1500M (32bit exe)
xeon -> up to 2000M

malloc a couple of blocks of size 100M:

whole process (100 M steps)
opteron -> 7700M (64bit exe) -> up to 2200 (32bit exe)
xeon -> 2700M

So one 'looses' 500M.

Feedback welcome,
Soeren


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Largest mallocs opteron vs. 32bit systems
  2004-04-27  6:24 Largest mallocs opteron vs. 32bit systems Soeren Sonnenburg
@ 2004-04-28  6:06 ` Soeren Sonnenburg
  0 siblings, 0 replies; 2+ messages in thread
From: Soeren Sonnenburg @ 2004-04-28  6:06 UTC (permalink / raw)
  To: linux-kernel

On Tue, 27 Apr 2004 06:24:24 +0000, Soeren Sonnenburg wrote:

> Hello...
> 
> I just did some tests trying to malloc() memory on an opteron and a xeon
> system...
> [...]
> So one 'looses' 500M.
> 
> Feedback welcome,
> Soeren


I just want to mention, that this is kernel 2.4.21 (including quite a
number of redhat patches...) and due to a miscomputation 100M should be
added to every number...

Also when I malloc in smaller blocks (ie. size 1M) I get closer to 3G on a
i386 system (like 29xxM).

Soeren



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-04-28  6:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-27  6:24 Largest mallocs opteron vs. 32bit systems Soeren Sonnenburg
2004-04-28  6:06 ` Soeren Sonnenburg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox