When you describe the first and second half of gc are you referring to the mark
and sweep phases?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+un
Nothing is obvious but there is something going on we don't understand. If
you have the time to create a simple reproducer the next step would be to
open an issue that contains the reproducer. Once the problem can be
reproduced locally it can be diagnosed.
On Wednesday, June 7, 2017 at 11:37:2
Xun Liu,
Are you able to post the actual trace here? I appreciate that it contains
information about your source code, so I can understand if you don't want
to share it. But I would be very interested to look at the full trace.
Thanks
Francis
On Wednesday, 31 May 2017 21:02:33 UTC+2, Xun Liu
gc 347 @6564.164s 0%: 0.89+518+1.0 ms clock, 28+3839/4091/3959+33 ms cpu,
23813->23979->12265 MB, 24423 MB goal, 32 P
What I'm seeing here is that you have 32 HW threads and you spend .89+518+1
or 520 ms wall clock in the GC. You also spend 28+3839+4091+3959+33 or
11950 ms CPU time out of total o
$ go version
go version go1.8 linux/amd64
On Wednesday, May 31, 2017 at 7:13:38 AM UTC-7, Ian Lance Taylor wrote:
>
> [ +rlh, austin ]
>
> Which version of Go are you running?
>
> Ian
>
> On Tue, May 30, 2017 at 10:01 PM, Xun Liu >
> wrote:
>
>> Hi, we see a clear correlation between GC and l
[ +rlh, austin ]
Which version of Go are you running?
Ian
On Tue, May 30, 2017 at 10:01 PM, Xun Liu wrote:
> Hi, we see a clear correlation between GC and latency spike in our Go
> server. The server uses fairly large amount of memory (20G) and does mostly
> CPU work. The server runs on a beef
Hi, we see a clear correlation between GC and latency spike in our Go
server. The server uses fairly large amount of memory (20G) and does mostly
CPU work. The server runs on a beefy box with 32 cores and the load is
pretty light (average CPU 20-30%). GC kicks in once every 10-20 seconds
and w
