-
Notifications
You must be signed in to change notification settings - Fork 177
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
New Selection Algorithm #2872
New Selection Algorithm #2872
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2872 +/- ##
===================================================
- Coverage 56.48581% 56.40748% -0.07833%
===================================================
Files 88 89 +1
Lines 19242 19368 +126
===================================================
+ Hits 10869 10925 +56
- Misses 7774 7839 +65
- Partials 599 604 +5
Continue to review full report in Codecov by Sentry.
|
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.
Really really neat change!
Changes:
-selectStakeWeight
,-selectPriceWeight
: weights of selection algorithms params-selectPriceExpFactor
: expresses how significant a small change of price is for the selection algorithm; default 100-orchPerfStatsUrl
: URL to the test stream service, Livepeer Inc service is available at:https://leaderboard-serverless.vercel.app/api/aggregated_stats
-minPerfScore
: filter for the minimal O's performance score to be accepted for the selection-region
: region where B is deployed; used to get the right performance scoresSome notes about the approach
selection=0.3*exp(price, 100)+0.4*rand+0.3*stake
, but I think we should wait for some more use-cases / feature request to decide on the best approach-minPerfScore
are taken into consideration for the selection. Note that the performance score is calculated as defined in https://github.com/livepeer/leaderboard-serverless, soperfScore = (RTT / segment_size) * success_rate
. At first, I thought we should use the RTT expressed inms
, but that's not a good metric, because RTT depends on the segment length, so the performance score sounds like a better metric for the performance