During the review of JDK-8194823, we find the serial GC doesn't implement the GC overheap limit during the GC operation. But it checks the GC overheap limit after the GC, which is unnecessary.
In detail, the GC operation in Serial GC doesn't use `GCOverheadChecker::check_gc_overhead_limit` and other related methods to change the fields `_gc_overhead_limit_count` and `_gc_overhead_limit_exceeded`. But after the GC, the method `GenCollectedHeap::mem_allocate_work` checks if the `_gc_overhead_limit_exceeded` is true, which is never true.
Seems a leftover after removing the CMS.
In detail, the GC operation in Serial GC doesn't use `GCOverheadChecker::check_gc_overhead_limit` and other related methods to change the fields `_gc_overhead_limit_count` and `_gc_overhead_limit_exceeded`. But after the GC, the method `GenCollectedHeap::mem_allocate_work` checks if the `_gc_overhead_limit_exceeded` is true, which is never true.
Seems a leftover after removing the CMS.
- relates to
-
JDK-8194823 Serial GC does not account GCs caused by TLAB allocation in GC overhead limit
-
- Closed
-
-
JDK-8309403 Serial: Remove the useless adaptive size policy in GenCollectedHeap
-
- Resolved
-
