Bug fix: printing non-distributed data #1756
Open
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.
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