Closed geekflyer closed 1 month ago
Hello! Thank you for filing an issue.
The maintainers will triage your issue shortly.
In the meantime, please take a look at the troubleshooting guide for bug reports.
If this is a feature request, please review our contribution guidelines.
Hey @geekflyer,
We are already working on improvements that should improve scaling performance. Closing this one as a duplicate of https://github.com/actions/actions-runner-controller/issues/3276
@nikola-jokic are you sure #3276 is the same? From the looks of it #3276 is about scaling delays under high job spikes. The issue I opened has nothing to do with spikes/high load, but rather is about the message processing delay when creating a single pod (under no load) from 0->1.
Hey @geekflyer,
Can you please check if this is happening again? I ran many jobs today and I haven't seen this delay.
I wanted to combine and link these two since they are both performance-based issues. Although I think the latency issue was a temporary problem, I closed this one and linked it to the one submitted before.
Checks
Controller Version
0.9.2
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
Listener is very slow to receive messages and spawn worker pods.
Describe the expected behavior
Listener should spawn worker pods immediately or with like max 5s delay after they've been submitted to github.com.
With the legacy summerwind controller and webhook-driven scaling the controller used to create new pods/scale up pretty much immediately. The new controller seems to be a large step back with regards to that, unless I'm missing somthing?
Controller Logs