You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(ai): Enhance orchestrator selection by incorporating latency (livepeer#3043)
This commit introduces latency consideration into the orchestrator
selection process, addressing two key issues. Firstly, it resolves a
minor bug where the algorithm consistently selected known orchestrators
due to a condition that never evaluated to true (see [this
condition](https://github.com/livepeer/go-livepeer/blob/1239b4e56133003fe6a98a863cce6bdd6b5f2532/server/selection.go#L110)).
Secondly, this change ensures that, once all orchestrators have been
evaluated, the one with the fastest response time for a specific job is
chosen. While the current method for calculating latency is somewhat
basic, it sets the foundation for more sophisticated enhancements in the
future.
Co-authored-by: Brad P <0xb79orch@gmail.com>
0 commit comments