-
Notifications
You must be signed in to change notification settings - Fork 68
Avoid seeking checks when decoding frames sequentially #1028
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
Merged
NicolasHug
merged 7 commits into
meta-pytorch:main
from
NicolasHug:avoid_seeking_checks
Nov 12, 2025
Merged
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
3e9ae6f
Avoid seeking checks when decoding frames sequentially
NicolasHug 86ec99e
Simplify seek skipping logic
NicolasHug e68d7ce
Merge branch 'main' of github.com:pytorch/torchcodec into avoid_seeki…
NicolasHug d98c78a
Merge branch 'simplify_skip' into avoid_seeking_checks
NicolasHug 42409a9
comment
NicolasHug 9acc148
Merge branch 'main' of github.com:pytorch/torchcodec into avoid_seeki…
NicolasHug 2295241
Fix
NicolasHug File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 file contains hidden or 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
Oops, something went wrong.
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.
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.
I included the changes from #1039 in this PR.
@scotts , does the comment make sense now? What the comment is not saying is why returning early in
canWeAvoidSeeking()is important. It's important because it avoids the calls toav_index_search_timestampwhich are potentially slow. I don't know if we want to get to that level of detail in the comment.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.
Yes, this greatly helps with understanding.
I do think we should explain somewhere that
canWeAvoidSeeking()is itself expensive in some circumstances. . That's deeply counter-intuitive, that the function we're calling as an optimization to avoid the slow thing is itself also a slow thing. (But hopefully less slow.) Perhaps that should belong at the top ofcanWeAvoidSeeking().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.
Will address that in an immediate follow-up