Troubles with Shenandoah

Roman Kennke rkennke at redhat.com
Sun Apr 7 19:45:10 UTC 2019


Actually, I am not quite clear what is the success scenario or the
failure scenario. Can you describe a little more detail what I should
watch out for for both cases? To me it behaves all ~the same (maybe
that means I failed to reproduce so far)

Roman

> Hi,
> 
> On Sun, Apr 7, 2019 at 6:54 PM Roman Kennke <rkennke at redhat.com>
> wrote:
> > I believe builds.Shipilev.net also has fastdebug builds.
> > 
> > Also, any idea what it gets stuck on?
> 
> No.
> 
> The web application is a chat application: it receives 1 message via
> HTTP request and sends that message to other 10 clients.
> Lots of short lives objects (HTTP request/response, gazillions of
> strings for headers/fields and such, messages converted to/from JSON,
> etc.).
> There are long-lived objects such as the client sessions on
> server-side and they have a queue of messages (also long-lived).
> No application exceptions and no crashes, and works with
> heuristics=passive, I frankly don't know what to think.
> Perhaps the server-side queues lose messages, and that's why the
> clients report that?
> 
> Will try the fastdebug build and report back.
> Is there anything special I need to set for the fastdebug run?
> 
> Thanks!
> 



More information about the shenandoah-dev mailing list