Strange G1 behavior

[Thomas Schatzl]

Hi Guillaume,

On Fri, 2017-10-20 at 15:03 +0200, Guillaume Lederrey wrote:
> Thanks for your continuing interest in our issue!

  thanks for giving us the opportunity to look at your workload, and
your time you spend on our requests.

> 
> I have been firefighting another issue with a user sending a bit too
> much traffic our way. Good news, this allowed us to tune our
> throttling and will probably result in a slightly smoother load in
> the future, which can only help...
> 
> I have prepared a change with your suggested improvements [1]. But I
> will wait until next Monday to deploy it. I'll send the new logs as
> soon as I have them.
> 
> Kirk suggested earlier to double the size of the heap (from 16GB to
> 32GB). I have not yet implemented that suggestion. Do you think it
> make sense to bundle that change with the changes suggested by
> Thomas? Or should I keep it for later?
> 

I would prefer if we did not change too many variables at the same
time. Heap size has (obviously) a huge impact on behavior, although in
this case we will always see whether the heap usage spikes/length of
marking etc.

The only problem is that it seems we won't get to see that user
generating these loads anymore, so it might be that some of these
suggestions may be unneeded (and to some degree detrimental to overall
performance).

But it's your setup :)

Thanks,
  Thomas