Strange behavior of garbage collector on go tip (go1.5beta1)

[Marko Kevac]

Hi.

We are using go tip as a way to reduce garbage collection times in our program. And it works: garbage collection times are ~10x smaller. But not always... Each day we see these spikes for a few hours. Garbage collection time grows from ~2ms to ~600ms. It repeats each day.

We could not find the culprit in our program, so I am asking here: is it something related to new GC in 1.5?

An upper chart shows garbage collection times in nanoseconds and is taken from http://.../debug/vars. The lower chart shows memory usage.

Marko

[r...@golang.org]

What is going on at different times of the day and what are the frequencies of the GCs with high latency. If high latency is correlated with low allocation and a GC frequency of 2 seconds we have a bug filed on that. If it is something else file an bug report.

[ma...@kevac.org]

GC frequency is indeed 2 minutes when GC times are high.
Can you give me a link to this bug, please?

Thanks!

On Fri, Jul 10, 2015 at 4:58 PM <r...@golang.org> wrote:

What is going on at different times of the day and what are the frequencies of the GCs with high latency. If high latency is correlated with low allocation and a GC frequency of 2 seconds we have a bug filed on that. If it is something else file an bug report.

--
You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golang-nuts/ImlznAr_cT4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rick Hudson]

#10261 is the issue. It was closed yesterday. If you could post the new numbers in a few days that would be great. Sorry about the 2 sec / 2 min confusion.

[ma...@kevac.org]

After updating to last tip, this strange behavior disappeared. Thank you.