Process batch jobs grouped by email address #101
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We previously processed batch jobs round robin, i.e., one item
for each job per round. This is fair from the job point of view,
but not from the user point of view when one user has many jobs.
We now process batch jobs one item for each user per round,
where we pick the oldest job if a user has more than one. Users
are defined by their email address.
Batch jobs submitted via the webservices all have the same email
address, so they are effectively throttled as if all from the
same user. Adapting the webservices to also allow setting an
email address is future work.