With a 500k machine cluster I suggest getting professional Go support - someone experienced in troubleshooting that can sit with you and review the code and configuration to diagnose the issue.
Personally it sounds like overallicated machines causing thrashing delays in the context switching. > On Jun 22, 2021, at 9:21 AM, Peter Z <zjy19871...@gmail.com> wrote: > > Sorry for a mistake: 'hyperthread closed', hyperthread is actually on. > > 在2021年6月22日星期二 UTC+8 下午10:01:48<Peter Z> 写道： >> 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, the >> agent process still hung there. >> >> 2021-6-22 Tue UTC+8 pm 8:06:55<jake...@gmail.com> ： >>> Sorry, now I am completely confused. >>> >>>>> 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. >>> >>> but then you say: "Only one process per machine". >>> >>> Is there a language barrier, or am I missing something? >>> > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/1732ca49-e526-4ec4-ac29-0f9a4b2f949cn%40googlegroups.com. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/24CB21C1-0DA5-4FE7-A824-0D406AE93CDB%40ix.netcom.com.
