Troubles with Shenandoah

[Simone Bordet]

Hi,

On Tue, Apr 9, 2019 at 10:20 AM Aleksey Shipilev <shade at redhat.com> wrote:
>
> On 4/8/19 11:05 PM, Aleksey Shipilev wrote:
> > On 4/8/19 10:54 PM, Simone Bordet wrote:
> >> Just to be clear, you had no problems with heap locked at max size and
> >> always pre-touch with 12+33?
> >
> > Correct. I used jdk12 binary [1] for testing:
> > 12-testing+0-builds.shipilev.net-openjdk-jdk12-b158-20190406-jdk-1233jdk-12-ga. Locking the heap
> > resolved the latency and lost messages problems for me. YMMV, so please try yourself.
> >
> >> batch count = 1_000 runs for ~10s.
> >> 8 hrs -> batch count = 2_880_000
> >>
> >> Make it 2_500_00 and you should be good overnight (I once did precise
> >> math and the "circa" 10s, when multiplied, yielded hours more :)
> >
> > Okay!
>
> I ran 2_500_000 batches overnight with jdk12 fastdebug build and full verification, without any trouble.

Ran 12+33 with -Xms==-Xmx and -XX+AlwaysPreTouch for 20+ mins without issues.

Now I'm just curious about what the previous settings triggered.

How come https://bugs.openjdk.java.net/browse/JDK-8222129 is not
triggered with this setup, but was with the previous?

Thanks!

-- 
Simone Bordet
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz