refactor: update texture processing to use time limit instead of item limit #502
Conversation
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
wouterlucas
requested review from
erikhaandrikman,
jfboeve and
michielvandergeest
wouterlucas
force-pushed
the
feat/texture-timelimit
branch
from
fdc36d9 to
72347e7
Compare
jfboeve
approved these changes
Jan 27, 2025
michielvandergeest
approved these changes
Jan 27, 2025
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.
Align to L2 time based approach.
Will use
textureProcessingTimeLimitby default set to10ms(just like L2) to process textures.Eg. under constraints generating mixed 1k nodes:
