Yeah, I did some digging when I had a free moment. The following is
the most germane to your issue.
5070823 poor malloc() performance for small byte sizes
-j
On Thu, May 01, 2008 at 05:36:26PM -0400, Matty wrote:
> We are building our application as a 32-bit entity on both Linux and
> S
We are building our application as a 32-bit entity on both Linux and
Solaris, so our
comparison should be apples to apples. Does anyone happen to know what the
bug id of the small malloc issue is? I searched the opensolaris bug
database, but
wasn't able to dig this up.
Thanks,
- Ryan
On Thu, Ma
Yipes! The 32-vs-64-bit thing bites us a lot when people are doing
Linux-to-Solaris comparisons.
If you just say "gcc" on Linux on a 64-bit CPU, you get a 64-bit binary. On
Solaris,
the default is 32-bit (even on a 64-bit CPU), unless you use -m64. This was
done for
maximum portability (32-b
Part of the problem is that these allocations are very small:
# dtrace -n 'pid$target::malloc:entry { @a["allocsz"] = quantize(arg0); }' -c
/tmp/xml
allocsz
value - Distribution - count
1 |
IMHO, it depends a lot on exactly what the app is doing.
I can think of a couple of possible reasons for the differences here:
- the time taken by the memory allocator itself (depends on how many, and what
sizes you're
asking for), and
- the exact placement of the memory can also (greatly) af
On Wed, Apr 30, 2008 at 6:26 PM, David Lutz <[EMAIL PROTECTED]> wrote:
> If your application is single threaded, you could try using the
> bsdmalloc library. This is a fast malloc, but it is not multi-thread
> safe and will also tend to use more memory than the default
> malloc. For a compari
results using Sun Studio 12.
Again, bsdmalloc is not multi-thread safe, so use it with caution.
HTH,
David
- Original Message -
From: Matty <[EMAIL PROTECTED]>
Date: Wednesday, April 30, 2008 2:22 pm
Subject: Re: [perf-discuss] Application runs almost 2x slower on Nevada than
Linux
To
On Mon, Apr 28, 2008 at 5:01 PM, <[EMAIL PROTECTED]> wrote:
> Hey Dude,
> I pulled down a copy of your test program and ran a few experiments.
>
> $ time ./xml
> 10 iter in 22.715982 sec
>
> real0m22.721s
> user0m22.694s
> sys 0m0.007s
>
> This seems to indicate that all of
Hey Dude,
I pulled down a copy of your test program and ran a few experiments.
$ time ./xml
10 iter in 22.715982 sec
real0m22.721s
user0m22.694s
sys 0m0.007s
This seems to indicate that all of our time is being spent in usermode, so
whatever it is in Solaris that is slower than L
Howdy,
I have been working with one of our developers to port a Linux application to
opensolaris. While benchmarking the app, we noticed that it ran 2x slower on
a Nevada build 85 host than it did on Linux. The application utilizes libxml to
transform XML documents, and I think we have narrowed do
10 matches
Mail list logo
