On Tue, Jan 6, 2009 at 7:19 AM, S h i v <[email protected]> wrote:
>
> Mapping the system level information that sar(1) has thrown into
> actual cause at process(or such) level has been the problem.
>
> Looking forward to get some insights.
>

On a side note, libgc.so (sun studio's garbage collection library) is
being used by the application for memory management.

Does this library scale well for multi-threaded applications?
I did not come across sufficient documentation for libgc.so,
especially zero information for comparing it with other memory
allocators(libmtmalloc.so, libc.so, libumem.so) and suitability for
different applications.
Does libgc.so follow any pattern in garbage collection that might
result in CPU fluctuations.

-Shiv
_______________________________________________
perf-discuss mailing list
[email protected]

Reply via email to