Skip to content
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

[Core feature] Investigate how to turn the PyTorch visualizer into a deck #6123

Open
2 tasks done
eapolinario opened this issue Dec 26, 2024 · 0 comments
Open
2 tasks done
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@eapolinario
Copy link
Contributor

Motivation: Why do you think this is important?

Huggingface announced a pytorch visualizer: https://huggingface.co/blog/train_memory. Now that we're approaching the ability to generate decks for failed executions, we should investigate if possibility of turning the pytorch visualizer into a deck.

Goal: What should the final outcome look like, ideally?

Investigate the possibility of rendering the profiling data generated by pytorch in a flyte deck.

Describe alternatives you've considered

Copy the profiling file to blob store and generate a link at the end of the execution.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@eapolinario eapolinario added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Dec 26, 2024
@eapolinario eapolinario added help wanted Extra attention is needed and removed untriaged This issues has not yet been looked at by the Maintainers labels Dec 26, 2024
@davidmirror-ops davidmirror-ops moved this from Backlog to Assigned in Flyte Issues/PRs maintenance Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Status: Assigned
Development

No branches or pull requests

1 participant