Track enhancement for optimizing job order reflection #461
Description
What you would like to be added?
- Recomputing job order in every session may add unnecessary overhead.
- An optimisation could be considered to make this more efficient, for example by exploring lazy computation, snapshots, or other approaches.
Next Steps:
- Gather performance statistics to understand the impact of the current approach.
- Discuss and evaluate possible optimization strategies.
Why is this needed?
During the review of PR #445
It was noted that the current implementation recalculates job orders in every scheduling session, even though the /get-job-order endpoint may not always be queried.