Skip to content
This repository has been archived by the owner. It is now read-only.

Allow to determine consequence of max worker limit #43

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

Allow to determine consequence of max worker limit #43

jonnor opened this issue Nov 18, 2015 · 2 comments
Milestone

Comments

@jonnor
Copy link
Member

@jonnor 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
Copy link
Member Author

@jonnor 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
Copy link
Member Author

@jonnor 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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant