Repeated ParNews when Young Gen is Empty?
Simone Bordet
simone.bordet at gmail.com
Mon Jul 29 14:36:09 PDT 2013
Hi,
On Mon, Jul 29, 2013 at 11:32 PM, Andrew Colombi <acolombi at palantir.com> wrote:
> All,
>
> The problem in production was resolved by reducing the amount of
> allocation we were doing, and thereby reducing the pressure on the garbage
> collector. The log output is still very strange to me, and we're going to
> continue to investigate the potential for a JVM bug.
>
> One cool thing this experience taught me is a new debugging technique to
> identify allocation hotspots. Basically, with a combination of PrintTLAB
> and jstacks, you can identify which threads are heavily allocating and
> what those threads are doing. We were able to pinpoint a small number of
> threads doing the lion's share of the allocations, and improve their
> efficiency.
Care to detail this one, perhaps with an example of yours ?
Thanks !
--
Simone Bordet
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless. Victoria Livschitz
More information about the hotspot-gc-use
mailing list