-
Notifications
You must be signed in to change notification settings - Fork 20.5k
feat: Add EnergyAwareScheduling
new algorithm with Junit tests
#5818
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5818 +/- ##
============================================
+ Coverage 72.40% 72.42% +0.01%
- Complexity 4983 4985 +2
============================================
Files 653 654 +1
Lines 17574 17597 +23
Branches 3386 3387 +1
============================================
+ Hits 12724 12744 +20
- Misses 4371 4372 +1
- Partials 479 481 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
for (Task task : tasks) { | ||
scheduledOrder.add(task.name); | ||
currentTime += task.executionTime; | ||
totalEnergyConsumption += currentTime * task.energyConsumption; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is consumed energy linearly proportional to the current time? The process should define when it consumes how much energy, or it should be defined somehow else. Please provide references where this algorithm is explained.
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution! |
Please reopen this pull request once you have made the required changes. If you need help, feel free to ask in our Discord server or ping one of the maintainers here. Thank you for your contribution! |
clang-format -i --style=file path/to/your/file.java