Skip to content
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

Benchmark Run Concurrency Queues #344

Closed
stanbrub opened this issue Sep 25, 2024 · 0 comments · Fixed by #349
Closed

Benchmark Run Concurrency Queues #344

stanbrub opened this issue Sep 25, 2024 · 0 comments · Fixed by #349
Assignees
Labels
enhancement New feature or request

Comments

@stanbrub
Copy link
Collaborator

With more developer (i.e. more than me) using adhoc benchmarks and more ways to run them, there is a possibility of stomping over existing runs when the same server is used for two runs. This is not a problem for auto-provisioned servers where a unique server is used for every adhoc run.

Resources:

@stanbrub stanbrub added the enhancement New feature or request label Sep 25, 2024
@stanbrub stanbrub self-assigned this Sep 25, 2024
@stanbrub stanbrub linked a pull request Oct 2, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant