-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Improve RichProgreasBar speed performance #21321
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
Open
GdoongMathew
wants to merge
13
commits into
Lightning-AI:master
Choose a base branch
from
GdoongMathew:fix/rich_progressbar
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
0e9a179
init fix
GdoongMathew c83a8f4
temp fix unittests
GdoongMathew 24c1729
release time sleep
GdoongMathew 47c3bd9
fix unittest
GdoongMathew e3b3100
ref soft_refresh
GdoongMathew f11e58f
fix test
GdoongMathew 86d823a
refactor _RefreshThread
GdoongMathew 2f24cb7
add type annotation
GdoongMathew 65e5f4f
Merge branch 'master' into fix/rich_progressbar
GdoongMathew daaacf9
add isinstance check
GdoongMathew fd959f2
Merge remote-tracking branch 'origin/fix/rich_progressbar' into fix/r…
GdoongMathew 3e2a851
Merge branch 'master' into fix/rich_progressbar
SkafteNicki 6c7108e
Merge branch 'master' into fix/rich_progressbar
justusschock 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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Looks great so far!
One minor question: can we make this configurable? so we/users can easily reduce this even more if required?
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.
What do you think about reusing the original
_RefreshThread.refresh_per_second, then exposing it as a configurable argument in theRichProgressBarcallback.One thing to note, this PR would also nullify the current
refresh_rateargument, since we are now auto-refreshing the progress withrefresh_per_secondfrequency.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.
couldn't we use the refresh_rate argument instead then? But yeah generally something like that I had in mind :)
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, that works. I believe this is also related to the discussion mentioned here. I agree that we should keep using
refresh_ratein this case, as long as we’re okay with updating its description, since it'll now represent the updates per second rather than current update frequency in number of batches?