We need to re-sort ready_list after updating all the priorities. Expensive, but no way around it I think.
PRI_UPDATE_FREQ is a separate value from TIME_SLICE, they just
happen to be set the same.
- We need to re-sort `ready_list` after updating all the priorities. Expensive, but no way around it I think.
- PRI_UPDATE_FREQ is a separate value from TIME_SLICE, they just
happen to be set the same.
LGTM!
We had a function to resort the ready list that was then removed as it turned out it was not necessary in our case.
It is also a good bet to resort even if it was unnecessary as O(n log n) will be better than repeated O(n) for large enough number of n.
LGTM!
We had a function to resort the ready list that was then removed as it turned out it was not necessary in our case.
It is also a good bet to resort even if it was unnecessary as O(n log n) will be better than repeated O(n) for large enough number of n.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ready_listafter updating all the priorities. Expensive, but no way around it I think.happen to be set the same.
approved this merge request
LGTM!
We had a function to resort the ready list that was then removed as it turned out it was not necessary in our case.
It is also a good bet to resort even if it was unnecessary as O(n log n) will be better than repeated O(n) for large enough number of n.
mentioned in commit
af31968e67