billions-insurance-43532
05/15/2024, 6:07 PMrefined-kangaroo-48640
05/15/2024, 9:41 PMGOMAXPROCS=1
?refined-kangaroo-48640
05/15/2024, 9:41 PMbillions-insurance-43532
05/15/2024, 9:44 PMGOMAXPROCS
but its a single core machine so it's likely deriving from that. Doesn't really explain the timeout though since it was working fine before with the "unlimited" spawnrefined-kangaroo-48640
05/15/2024, 9:49 PMGOMAXPROCS
maximum pool size, so that could be the problem. Before, it was spawning an unlimited number of processes, one per request, with a correspondingly poor latency impact. Try increasing GOMAXPROCS to 10billions-insurance-43532
05/15/2024, 9:50 PMrefined-kangaroo-48640
05/15/2024, 9:51 PMbillions-insurance-43532
05/15/2024, 9:52 PMrefined-kangaroo-48640
05/15/2024, 9:52 PMbillions-insurance-43532
05/15/2024, 9:52 PMrefined-kangaroo-48640
05/15/2024, 9:52 PMrefined-kangaroo-48640
05/15/2024, 9:53 PMbillions-insurance-43532
05/15/2024, 9:53 PM