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

Track average scheduling delay when accepting tasks. #1583

merged 4 commits into from Jul 14, 2017


Copy link

@baconmania baconmania commented Jul 5, 2017

No description provided.

long now = System.currentTimeMillis();

if (bldr.getAverageSchedulingDelayMillis().isPresent()) {
long newAverageSchedulingDelayMillis = (bldr.getAverageSchedulingDelayMillis().get() * bldr.getNumTasks() + (now - dueTime)) / (bldr.getNumTasks() + 1);

This comment has been minimized.


ssalinas Jul 5, 2017

this could get funky along with tracking the avgRunTime. We would be incrementing the numTasks when the tasks were finished, but updating this based on when they were started. Might want to track a separate numTasks for this

…tain two separate numTasks counts.
Copy link

@ssalinas ssalinas commented Jul 6, 2017


@ssalinas ssalinas modified the milestone: 0.17.0 Jul 14, 2017
@ssalinas ssalinas merged commit 9b68200 into master Jul 14, 2017
1 of 2 checks passed
1 of 2 checks passed
continuous-integration/travis-ci/push The Travis CI build failed
continuous-integration/travis-ci/pr The Travis CI build passed
@ssalinas ssalinas deleted the average-scheduling-delay branch Jul 14, 2017
@baconmania baconmania modified the milestones: 0.18.0, 0.17.0 Sep 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.