My current theory, which I haven't dug into the source to confirm, is that
said buffers are being pre-allocated. Because the kafka instance is
relatively bored, they end up living long enough to see a few collections
and be promoted. I could be way off base though.
Command line, broken out for a l
We've had no problems with G1 in all of our clusters with varying load
levels. I think we've seen an occasional long GC here and there, but
nothing recurring at this point.
What's the full command line that you're using with all the options?
-Todd
On Wed, Oct 14, 2015 at 2:18 PM, Scott Clasen
You can also use -Xmn with that gc to size the new gen such that those
buffers don't get tenured
I don't think that's an option with G1
On Wednesday, October 14, 2015, Cory Kolbeck wrote:
> I'm not sure that will help here, you'll likely have the same
> medium-lifetime buffers getting into the
I'm not sure that will help here, you'll likely have the same
medium-lifetime buffers getting into the tenured generation and forcing
large collections.
On Wed, Oct 14, 2015 at 10:00 AM, Gerrit Jansen van Vuuren <
gerrit...@gmail.com> wrote:
> Hi,
>
> I've seen pauses using G1 in other applicatio
Hi,
I've seen pauses using G1 in other applications and have found that
-XX:+UseParallelGC
-XX:+UseParallelOldGC works best if you're having GC issues in general on
the JVM.
Regards,
Gerrit
On Wed, Oct 14, 2015 at 4:28 PM, Cory Kolbeck wrote:
> Hi folks,
>
> I'm a bit new to the operational
