JDK-8145534 : TestRemsetLogging.java takes a long time
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-12-16
  • Updated: 2016-01-28
  • Resolved: 2015-12-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b103Fixed
Related Reports
Relates :  
JDK-8145092 - Use Unified Logging for the GC logging
Description
With the changes to use the unified logging framework for the GC logging (JDK-8145092) the test TestSummarizeRSetStats.java was renamed to TestRemsetLogging.java and updated to use the new logging.

Running on linux x64 with fastdebug builds I get the following:

Before JDK-8145092: elapsed time (seconds): 0.457
After JDK-8145092: elapsed time (seconds): 18.698
Comments
Turns out that this is not a regression introduced by JDK-8145092. The "Before" time above is from JDK1.9-b36 where G1 was not default. The test does an early exit if G1 is not being used. Using b94, where G1 is default but the new logging changes are not included, I get: elapsed time (seconds): 18.276 So, pretty much the same as before. This is still way too long for a JTreg test, but it is not related to JDK-8145092.
16-12-2015