Oh nice, I'll check that out.
On Thu, Aug 30, 2018 at 11:07 AM Jonathan Haddad wrote:
> Advertised, yes, but so far I haven't found it to be any better than
> ParNew + CMS or G1 in the performance tests I did when writing
> http://thelastpickle.com/blog/2018/08/16/java11.html.
>
> That said, I d
Advertised, yes, but so far I haven't found it to be any better than
ParNew + CMS or G1 in the performance tests I did when writing
http://thelastpickle.com/blog/2018/08/16/java11.html.
That said, I didn't try it with a huge heap (i think it was 16 or 24GB), so
maybe it'll do better if I throw 50
https://www.opsian.com/blog/javas-new-zgc-is-very-exciting/
.. max of 4ms for stop the world, large terabyte heaps, seems promising.
Will this be a major boon to cassandra p99 times? Anyone know the aspects
of cassandra that cause the most churn and lead to StopTheWorld GC? I was
under the impres
In the meanwhile, do you think you could highlight the features of your repair
solution / sidecar?
Dinesh
> On Aug 30, 2018, at 4:57 AM, Marcus Olsson wrote:
>
> Great to see that there is an interest! As there currently are some internal
> dependencies etc. in place there is still some work
Great to see that there is an interest! As there currently are some internal
dependencies etc. in place there is still some work to be done before we can
publish it. I would expect this to take at least a few weeks, to try set the
correct expectations.
Best Regards
Marcus Olsson
On tis, 2018-0
Hey Sumanth,
could you clear a few things up for me…
> C* 2.2
> > I'm still a bit confused as to what's the benefit in compiling with
> > jdk1.7 and then testing with jdk1.7 or jdk1.8
>
> I meant two separate workflows for each JDK i.e.
> Workflow1: Build against jdk1.7, and optionally run UTs
