JDK-8150776 : [TESTBUG] stress/gc/TestStressRSetCoarsening.java takes too long to run
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • Submitted: 2016-02-27
  • Updated: 2016-08-02
  • Resolved: 2016-08-02
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
9Resolved
Related Reports
Relates :  
JDK-8134963 - [Newtest][TEST_BUG] New stress test for changing the coarseness level of G1 remembered set
Description
It seems this test take too long to run on hosts with large number of cores and memory. In one of my recent RBT runs, on a 2 socket Xeon X5675 @ 3.07GHz (12 HT per socket) with 74 GB RAM, this test took over 3 hours to run. This has a serious impact on nightly test execution.
Comments
The test has been modified several times since the date of the bug submission. I can't reproduce the problem from description. So, I'm closing the issue as will not fix.
02-08-2016
The test is known to be slow. It starts VM several times, each time it limits heap (Xmx500m or Xmx1G), so it's prepared to be executed with large heaps. So, there is nothing wrong with the test itself but we need a mechanism to prevent the situation when a single test slows the entire run.
29-02-2016