JDK-8256327 : Revisit aggressive code cache sweeping behaviour
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 16
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2020-11-13
  • Updated: 2022-03-14
  • Resolved: 2022-03-14
Related Reports
Duplicate :  
JDK-8271008 - appcds/*/MethodHandlesAsCollectorTest.java tests time out because of excessive GC (CodeCache GC Threshold) in loom
Description
Running a big IDE I have noticed the code cache being close to full. The aggressive sweeping is triggered by the non-profiled code-heap being 90% full, but there is still a lot of room in the profiled-heap.

Non-profiled code can be allocated in the profiled-heap. Aggressive sweeping shouldn't be triggered before the combined space is starting to run out.

Changing this allows for more effective use of codecache space.
Comments
This has been addressed in https://bugs.openjdk.java.net/browse/JDK-8271008
09-03-2022