RFR: 8065331: Add JVM trace events for failed allocations

Jon Masamitsu jon.masamitsu at oracle.com
Wed Apr 1 14:44:13 UTC 2015


Marcus,

These changes are rather extensive and the CR is rather thin
on details.  How will the GC count information be useful?
Is it critical that it be the total GC count for failed allocation?
Could some partial GC count that does not require such
extensive changes be almost as useful?

Thanks.

Jon

On 3/30/2015 3:54 PM, Marcus Larsson wrote:
> Ping!
>
> ----- Original Message -----
> From: marcus.larsson at oracle.com
> To: hotspot-gc-dev at openjdk.java.net
> Sent: Tuesday, 24 March, 2015 7:35:08 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
> Subject: RFR: 8065331: Add JVM trace events for failed allocations
>
> Hi,
>
> Please review the following patch adding new trace events for allocations requiring GC, and GCs triggered by allocation. See the JEP for a description of these two new events.
>
> CR:
> https://bugs.openjdk.java.net/browse/JDK-8065331
>
> Webrev:
> http://cr.openjdk.java.net/~mlarsson/8065331/webrev.00/
>
> JEP:
> https://bugs.openjdk.java.net/browse/JDK-8060092
>
> Tests:
> jprt, jtreg
>
> Thanks,
> Marcus



More information about the hotspot-gc-dev mailing list