We detected this problem once again, and this time we observed the stacks.
See https://github.com/golang/go/issues/40372 for the details.
On Friday, May 22, 2020 at 3:25:39 PM UTC+8 Jan Mercl wrote:
> On Fri, May 22, 2020 at 9:05 AM tokers wrote:
> >
> > Thanks for you reply.
> >
> > Yeah, we
On Fri, May 22, 2020 at 9:05 AM tokers wrote:
>
> Thanks for you reply.
>
> Yeah, we have the plan to upgrade our go version to 1.13.10.
Note that 1.13 does not have goroutine preemption Ian was talking
about wrt 1.14.
--
You received this message because you are subscribed to the Google
Thanks for you reply.
Yeah, we have the plan to upgrade our go version to 1.13.10.
--
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
On Thu, May 21, 2020 at 8:55 PM tokers wrote:
>
> We have a go program (an api server) on a virtual machine(with 8 cores) with
> a long time stable running.
> However, the program recently suffered a weird problem that only a single CPU
> reached 100%
> usage while others were very low, in the
Hi!
We have a go program (an api server) on a virtual machine(with 8 cores)
with a long time stable running.
However, the program recently suffered a weird problem that only a single
CPU reached 100%
usage while others were very low, in the meanwhile, the network bandwidth
was totally zero,
