forked from livepeer/go-livepeer
-
Notifications
You must be signed in to change notification settings - Fork 0
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
rebasing to latest main #2
Merged
JJassonn69
merged 24 commits into
JJassonn69:frame-interpolation-go
from
livepeer:ai-video
Oct 1, 2024
Merged
rebasing to latest main #2
JJassonn69
merged 24 commits into
JJassonn69:frame-interpolation-go
from
livepeer:ai-video
Oct 1, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds support for the new [segment anything 2](https://ai.meta.com/sam2/) pipeline (SAM2) that was added to the AI-worker in [this pull request](livepeer/ai-worker#185). While the new SAM pipeline can also do video segmentation this will be done in a subsequent pull request. Co-authored-by: John | Elite Encoder <[email protected]> Co-authored-by: Peter Schroedl <[email protected]> Co-authored-by: Rick Staa <[email protected]>
This commit released the new AI network software.
We don't want our gcp buckets to get overfilled with builds from external devs.
Not all fields will be identical segment-to-segment, particularly DurationSecs. This caused unnecessary transcoder re-initialization.
* Update LPMS to latest. * protoc: Regenerate
* Clean up inactive sessions Not cleaning up the sessions causes quite a big memory leak which in effect causes OOMKilled * Clean up inactive sessions Not cleaning up the sessions causes quite a big memory leak which in effect causes OOMKilled
…cy score (#3086) 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) Co-authored-by: Thom Shutt <[email protected]>
This commit updates the ai-worker to the one with the changed worker types.
This reverts commit e01daa2.
This commit ensures that the go-livepeer code uses the new worker classes that were defined in livepeer/ai-worker#191.
This commit introduces a mechanism for gateways to configure the timeout during the discovery process. It adds the `DiscoveryTimeout` CLI argument, with a default value of 500ms, consistent with the previous codebase.
This commit updates the AI error handling behavoir so that BadRequest errors are forwarded to the user. Co-authored-by: Rick Staa <[email protected]>
This commit cleansup the broadcaster and NewSessionManager code by removing the selection factory that has been unused since fea5673.
While merging the main branch into the AI branch, the fragile AI selection algorithm broke due to changes in the transcoding selection logic, which the AI algorithm relies on. This commit provides a temporary patch to ensure the selection process continues to function while we work on improving the AI selection algorithm.
Add ochestrator_version tag to ai_request_latency_score and ai_request_errors metrics
JJassonn69
pushed a commit
that referenced
this pull request
Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this pull request do? Explain your changes. (required)
Specific updates (required)
How did you test each of these updates (required)
Does this pull request close any open issues?
Checklist:
make
runs successfully./test.sh
pass