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

Allow to determine consequence of max worker limit #43

Open
jonnor opened this Issue Nov 18, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@jonnor
Member

jonnor commented Nov 18, 2015

To get an idea about what message rates/levels one can sustain with a particular config.
Should say something about what the limit (jobs/second) is when hitting max workers.

Maybe also how much delayed jobs would be if a sustained over-limit rates occur?

@jonnor

This comment has been minimized.

Show comment
Hide comment
@jonnor

jonnor Nov 18, 2015

Member

Related, relatively simple is to allow modifying the config, especially for 'simulating' different possible scenarios - maybe that could incur due to changes in the service-under-scaling itself. What if processing took twice as long on average.

Member

jonnor commented Nov 18, 2015

Related, relatively simple is to allow modifying the config, especially for 'simulating' different possible scenarios - maybe that could incur due to changes in the service-under-scaling itself. What if processing took twice as long on average.

@jonnor

This comment has been minimized.

Show comment
Hide comment
@jonnor

jonnor Mar 15, 2016

Member

Might also want to validate that the configuration can sustain a certain maximal input rate.

Member

jonnor commented Mar 15, 2016

Might also want to validate that the configuration can sustain a certain maximal input rate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment