-
Notifications
You must be signed in to change notification settings - Fork 55
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
Bug fix: printing non-distributed data #1756
Conversation
Thank you for the PR! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1756 +/- ##
=======================================
Coverage 92.26% 92.26%
=======================================
Files 84 84
Lines 12445 12447 +2
=======================================
+ Hits 11482 11484 +2
Misses 963 963
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Thank you for the PR! |
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.
For me this looks fine and co-pilot agrees.
Thx 👍
Thank you for the PR! |
Successfully created backport PR for |
* make 1-proc print great again * fix tabs size * skip formatter on non-distr data * remove time import (cherry picked from commit 3082dd9)
Backport failed for |
* make 1-proc print great again * fix tabs size * skip formatter on non-distr data * remove time import (cherry picked from commit 3082dd9) Co-authored-by: Claudia Comito <[email protected]>
Due Diligence
benchmarks: created for new functionalitydoes not applyDescription
I noticed that printing out moderately large DNDarrays in non-distributed mode (i.e. interactive session or split=None) takes a disproportionate amount of time (see below) compared to printing the underlying tensor. Culprit is the
Formatter
call.I've changed the printing module to bypass
Formatter
if the input dndarray is not distributed. Torch takes care of the data formatting, tests pass.Example:
On 1 process:
main
branch: 84 secondsthis PR: 0.01 seconds
Issue/s resolved: #
Changes proposed:
Type of change
Memory requirements
NA
Performance
see above
Does this change modify the behaviour of other functions? If so, which?
no