RFR: 8284404: Too aggressive sweeping with Loom [v2]

[Erik Österlund]

> The normal sweeping heuristics trigger sweeping whenever 0.5% of the reserved code cache could have died. Normally that is fine, but with loom such sweeping requires a full GC cycle, as stacks can now be in the Java heap as well. In that context, 0.5% does seem to be a bit too trigger happy. So this patch adjusts that default when using loom to 10x higher.
> If you run something like jython which spins up a lot of code, it unsurprisingly triggers a lot less GCs due to code cache pressure.

Erik Österlund has updated the pull request incrementally with one additional commit since the last revision:

  Add comment

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/8673/files
  - new: https://git.openjdk.org/jdk/pull/8673/files/461f8a30..4613da71

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=8673&range=01
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=8673&range=00-01

  Stats: 4 lines in 1 file changed: 4 ins; 0 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/8673.diff
  Fetch: git fetch https://git.openjdk.org/jdk pull/8673/head:pull/8673

PR: https://git.openjdk.org/jdk/pull/8673