-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Register processes for cleanup #153
Conversation
5fe6756
to
6f1dc5b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice find!
main thing i'm wondering: what would happen if we didn't have the limit and instead updated the code to always Wait()
but still allow any number of children to be launched? it'd remove the need for the pool. but perhaps it's not advisable ...
left comments with not doing ☝️ in mind 🙂
a11ccba
to
1decf46
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
alright! thanks for the updates. I'm scared about using more goroutines but the best thing to do might be to try it out
just had a couple of comments on the 429
Co-authored-by: Iain Lane <iain@orangesquash.org.uk>
24ccad3
to
2287189
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's give it a go 👍
The idea here is to register k6 TestRuns, for which we do not want to wait for a result, with a cleanup routine so that no zombie processes stay around.
Right now the number of handler go-routines (those that wait for the TestRun processes) are limited in number. If that limit is reached, then the HTTP handler becomes blocking.
Tasks
Resolves #152