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

Time budget(s) for stress testing #27

Closed
nicholzk opened this issue Dec 4, 2017 · 1 comment
Closed

Time budget(s) for stress testing #27

nicholzk opened this issue Dec 4, 2017 · 1 comment

Comments

@nicholzk
Copy link

nicholzk commented Dec 4, 2017

Would the performance of the stress testing use-case be evaluated over a range of increasing time budgets? If that is the case, could we have an idea of the ranges to be considered?

Alternatively, is there a single time budget we should optimise for?

@m8pple
Copy link
Contributor

m8pple commented Dec 6, 2017

Good point - that wasn't explicitly specified, and the random ranges chosen are
a bit shorter than I actually use for full testing.

My plan is to test for values in the range 2..180 seconds - I'd like to have done
a bit longer, but rabbit starts to have odd behaviour for n > 2^40, and I
think that keeps it in the range where things are still well behaved, even for
fast implementations.

I'll update the spec to reflect this, thanks for pointing it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants