Skip to content
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

selection: Clear known sessions if none of them has good enough latency score #3086

Merged
merged 3 commits into from
Sep 10, 2024

Commits on Jun 26, 2024

  1. selection: Clear known sessions if none of them has good enough laten…

    …cy score
    
    Problem: We never cleaned the known sessions, even if all of them had too low latency score to use; example of what sometimes happens:
    1) Broadcaster accumulated 8 known sessions, but all had too low latency score
    2) Session refresh was not triggered because we had a lot of knows session in the pool
    3) At the same time, we didn't have sessions in unknown session pool
    4) Selection checked that it cannot use the known session and tried to select from unknown sessions (but the pool was empty or there were no sessions fulfilling the condition of max price or perf score)
    leszko committed Jun 26, 2024
    Configuration menu
    Copy the full SHA
    90c8d2a View commit details
    Browse the repository at this point in the history

Commits on Sep 10, 2024

  1. Configuration menu
    Copy the full SHA
    b038843 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    97bf818 View commit details
    Browse the repository at this point in the history