Sorry for a mistake: 'hyperthread closed', hyperthread is actually on.
在2021年6月22日星期二 UTC+8 下午10:01:48 写道：
> I just checked the monitor data and found that the machine suffered from
> high 'load average'(about 30+) at approximately the time the agent get
> stuck.
> A 24 cores(2 CPUs * 14 cores)
I just checked the monitor data and found that the machine suffered from
high 'load average'(about 30+) at approximately the time the agent get
stuck.
A 24 cores(2 CPUs * 14 cores), hyperthread closed machine with load average
over 30 seems bad. But after the load average got down to below 1, th
>
> He is stating he has a cloud cluster consisting of 500k machines - each
> machine runs an agent process - each agent has 7000 Go routines.
>
Aha. Yes, this is what I mean.
> Sorry, now I am completely confused.
>
> So, you have about 500,000 *processes *running this agent on each
>>> ma
It seems like scheduling latency to me.
>
> On Jun 21, 2021, at 6:31 AM, Peter Z wrote:
>
>
>
> So, you have about 500,000 *processes *running this agent on each
>> machine, and each process has around 7,000 gorouines? Is that correct?
>>
>
> Yes, that's exact
>
> So, you have about 500,000 *processes *running this agent on each
> machine, and each process has around 7,000 gorouines? Is that correct?
>
Yes, that's exactly what I mean.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe
>
> On Thu, Jun 17, 2021 at 9:19 AM Peter Z wrote:
> >
> > The original post is on stackoverflow
> https://stackoverflow.com/questions/67999117/unexpected-stuck-in-sync-pool-get
>
> >
> > Golang ENV:
> > go1.14.3 linux/amd64
> >
> >
The original post is on stackoverflow
https://stackoverflow.com/questions/67999117/unexpected-stuck-in-sync-pool-get
Golang ENV:
go1.14.3 linux/amd64
Description:
We have about half a million agents running on each of our machines.The
agent is written in Go. Recently we found that the agent
