RFR: 8265349: vmTestbase/../stress/compiler/deoptimize/Test.java fails with OOME due to CodeCache exhaustion. [v3]

[Igor Ignatyev]

On Thu, 29 Apr 2021 09:24:12 GMT, Evgeny Nikitin <enikitin at openjdk.org> wrote:

>> The bug: https://bugs.openjdk.java.net/browse/JDK-8265349
>> 
>> A repetition of the JDK-8058176 (mlvm tests cause code cache exhaustion), this time with -Xcomp. My measurements show up max code cache consumption of 400-500 kb per test thread and tree (depends on random tree and other factors, of course, but still). For the whole test which usually doesn't exceed 10 threads, I've got max. value of 6.1M for one sequence/tree build (between checks for remaining free space).
>> 
>> So I suggest to raise the allowances to 10M, just to be safe. Compared to the 103 Mb of required code cache space that test requests via the 'run' parameter, it doesn't look that much.
>> 
>> Thanks in advance,
>> // Evgeny Nikitin.
>
> Evgeny Nikitin has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Explain limits numbers, extract code cache monitoring into a class

other than a typo, LGTM.

test/hotspot/jtreg/vmTestbase/vm/mlvm/meth/share/MHTransformationGen.java line 92:

> 90:         // |      10        |    1 - 2 M    |    5-6 M   |
> 91:         //
> 92:         // Those numbers are approximate (since threes are generated randomly and the total consumption

s/threes/trees/ ?

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

Marked as reviewed by iignatyev (Reviewer).

PR: https://git.openjdk.java.net/jdk/pull/3762