Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Sujay GadSujay GadReporter
Jeelan PoolaJeelan Poola(Deactivated)Is this a Regression?
UnknownTriage
UntriagedStory Points
1Priority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Sujay Gad
Sujay GadReporter
Jeelan Poola
Jeelan Poola(Deactivated)Is this a Regression?
Unknown
Triage
Untriaged
Story Points
1
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created May 30, 2022 at 4:29 AM
Updated October 7, 2022 at 8:53 AM
Resolved May 31, 2022 at 5:10 AM
As part of addressing in 7.1.1, the services need to respect the value of the GOMAXPROCS env var if specified. FTS does this in a simple way here, though it seems a bit unnecessary as according to https://pkg.go.dev/runtime#GOMAXPROCS, the GOMAXPROCS default is runtime.NumCPU anyway. Query does it in a slightly more complicated fashion here, but it looks like it also works.
On first look at the code, it appears eventing-producer process already honors whatever is set in GOMAXPROCS. The part that's not very clear is how CPU utilisation of eventing-consumer processes (as many as number of deployed functions) can be controlled. It appears, linux cgroup itself should take care of it. But we should analyse if there are any implications. Finally, eventing memory quota should be set as MIN(eventing-quota, cgroup_mem_limit)