Tue, 14 Oct 2014 20:35:45 +0000 Merge
jwilhelm [Tue, 14 Oct 2014 20:35:45 +0000] rev 27155
Merge
Tue, 14 Oct 2014 20:58:43 +0200 8027428: Different conditions for printing taskqueue statistics for parallel gc, parNew and G1
jwilhelm [Tue, 14 Oct 2014 20:58:43 +0200] rev 27154
8027428: Different conditions for printing taskqueue statistics for parallel gc, parNew and G1 Summary: Changed flag names for printing taskqueue and termination statistics for parallel gc, parNew and G1. Reviewed-by: jwilhelm, brutisso, tschatzl Contributed-by: sangheon.kim@oracle.com
Tue, 14 Oct 2014 19:55:54 +0200 8060116: After JDK-8047976 gc/g1/TestSummarizeRSetStatsThreads fails
mlarsson [Tue, 14 Oct 2014 19:55:54 +0200] rev 27153
8060116: After JDK-8047976 gc/g1/TestSummarizeRSetStatsThreads fails Summary: Also reviewed by: sangheon.kim@oracle.com Reviewed-by: brutisso
Mon, 13 Oct 2014 16:05:46 +0200 Merge
jwilhelm [Mon, 13 Oct 2014 16:05:46 +0200] rev 27152
Merge
Fri, 10 Oct 2014 12:15:51 +0200 8058801: G1TraceReclaimDeadHumongousObjectsAtYoungGC only prints humongous object liveness output when there is at least one candidate humongous object
tschatzl [Fri, 10 Oct 2014 12:15:51 +0200] rev 27151
8058801: G1TraceReclaimDeadHumongousObjectsAtYoungGC only prints humongous object liveness output when there is at least one candidate humongous object Summary: If G1TraceReclaimDeadHumongousObjectsAtYoungGC is enabled, always print humongous object liveness output. Reviewed-by: tschatzl Contributed-by: sangheon.kim@oracle.com
Thu, 09 Oct 2014 13:06:15 -0700 8057737: Avoid G1 write barriers on newly allocated objects
mgerdin [Thu, 09 Oct 2014 13:06:15 -0700] rev 27150
8057737: Avoid G1 write barriers on newly allocated objects Reviewed-by: mgerdin, kvn, iveresov Contributed-by: Staffan Friberg <staffan.friberg@oracle.com>
Thu, 09 Oct 2014 11:40:11 +0200 8059758: Footprint regressions with JDK-8038423
tschatzl [Thu, 09 Oct 2014 11:40:11 +0200] rev 27149
8059758: Footprint regressions with JDK-8038423 Summary: Changes in JDK-8038423 always initialize (zero out) virtual memory used for auxiliary data structures. This causes a footprint regression for G1 in startup benchmarks. This is because they do not touch that memory at all, so the operating system does not actually commit these pages. The fix is to, if the initialization value of the data structures matches the default value of just committed memory (=0), do not do anything. Reviewed-by: jwilhelm, brutisso
(0) -10000 -3000 -1000 -300 -100 -30 -10 -7 +7 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip