Allow to determine consequence of max worker limit #43

Open
jonnor opened this Issue Nov 18, 2015 · 2 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 jonnor added the enhancement label Nov 18, 2015
@jonnor jonnor modified the milestone: 0.2 Nov 18, 2015
@jonnor
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 jonnor added a commit that referenced this issue Mar 13, 2016
@jonnor jonnor config: Add some simple rate estimation
References #43
160c4dc
@jonnor
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