RFR: ShenandoahOOMDuringEvacALot

Roman Kennke rkennke at redhat.com
Tue Oct 24 18:06:33 UTC 2017


Am 24.10.2017 um 13:38 schrieb Aleksey Shipilev:
> On 10/23/2017 06:45 PM, Roman Kennke wrote:
>> When I made my prototype I added some diagnostics code to provoke the failure path for
>> OOM-during-evac very frequently. This proved to be very useful. I extracted this part from that
>> change and post it here because I think it's useful, whichever way we go with the bit-mangling patch.
>>
>> http://cr.openjdk.java.net/~rkennke/oomalot/webrev.00/
> Looks good, except for:
>
>   *) TestGCBasherWithShenandoah, TestGCLockerWithShenandoah, TestGCOldWithShenandoah:
>     Combining "aggressive" and "ShenandoahVerify" explodes the testing time.
Aha, oops ;-)

http://cr.openjdk.java.net/~rkennke/oomalot/webrev.01/ 
<http://cr.openjdk.java.net/%7Erkennke/oomalot/webrev.01/>

Good to go now? Or need 2nd reviewer?

Roman


More information about the shenandoah-dev mailing list