[PyTorch Debug] Fix the issue with PP

[pggPL]

Description

Simple fix for PP.

Fixes # (issue)

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

Please list the changes introduced in this PR:

• Change A
• Change B

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[pggPL]

/te-ci pytorch

[lengerfulluse]

# .internal = True is slightly faster, but results
# in errors when caching the weights.

@pggPL thanks for working on this. The PP > 1 verified worked when i set to False. But wondering whether you have some metrics on the throughput impact on this when you commented with slightly faster

[pggPL]

@lengerfulluse we use internal=False to mitigate CPU overhead with creating tensor object. It should not affect layers in iterations without logging and the overhead for logged layers should be much smaller than other overhead of logging.