Troubles with Shenandoah
Simone Bordet
simone.bordet at gmail.com
Mon Apr 8 20:54:18 UTC 2019
Hi,
On Mon, Apr 8, 2019 at 10:43 PM Aleksey Shipilev <shade at redhat.com> wrote:
> This was with batch-count=10K. I did run several iterations of it, spanning around an hour (lots of
> [Enters] pressed), and there are no lost messages. It used to be every 5-th run ending with lost
> msgs. What would be a good stress test to run overnight? batch-count=10M?
Just to be clear, you had no problems with heap locked at max size and
always pre-touch with 12+33?
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 :)
> I'd say for evaluation use, you can continue with jdk12u binary and always-committed-heap, unless
> you experience another problem.
Do you mean the tip of http://hg.openjdk.java.net/jdk-updates/jdk12u/?
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
More information about the shenandoah-dev
mailing list