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.

Sign up for GitHub

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

Jump to bottom

Use Compilation Groups to indicate what operations a TRT engine executes #47

Closed
narendasan opened this issue Apr 28, 2020 · 9 comments
Closed

Use Compilation Groups to indicate what operations a TRT engine executes #47

narendasan opened this issue Apr 28, 2020 · 9 comments
Assignees
@bowang007
Labels
component: core Issues re: The core compiler feature request New feature or request help wanted Extra attention is needed No Activity priority: low Will be handled, but not in the near term

Comments

@narendasan
Copy link
Collaborator

To help debugging it would be great to use compilation groups to indicate the work a TRT engine is doing. (This is a good tutorial on this https://jott.live/markdown/Writing%20a%20Toy%20Backend%20Compiler%20for%20PyTorch)
@narendasan narendasan added feature request New feature or request help wanted Extra attention is needed component: core Issues re: The core compiler priority: low Will be handled, but not in the near term labels Apr 28, 2020
@github-actions
Copy link

github-actions bot commented Jun 4, 2020

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

github-actions bot commented Jul 6, 2020

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@narendasan narendasan added this to the v0.3.0 milestone Jul 9, 2020
@github-actions
Copy link

github-actions bot commented Aug 9, 2020

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@narendasan narendasan reopened this Oct 29, 2020
@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

github-actions bot commented Apr 5, 2021

This issue has not seen activity for 90 days, Remove stale label or comment or this will be closed in 10 days

@narendasan narendasan modified the milestones: v0.3.0, v0.4 Jun 10, 2021
@narendasan narendasan removed this from the v0.4.0 milestone Aug 24, 2021
@github-actions
Copy link

This issue has not seen activity for 90 days, Remove stale label or comment or this will be closed in 10 days

@github-actions github-actions bot closed this as completed Dec 3, 2021
frank-wei pushed a commit that referenced this issue Jun 4, 2022
Various minor improvements to fx2trt lowering (#47)
629cf13 
Summary:
Pull Request resolved: https://github.com/pytorch/fx2trt/pull/47

- Make lowering log less verbose
- Support different dtype for cumsum

Although I think cumsum lowering is making things *slower*! We should just make a pytorch plugin for it.

Reviewed By: wushirong

Differential Revision: D35458649

fbshipit-source-id: 502d09ab98f6a4a288931d59670c01fe39a2e153
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bowang007 bowang007

Labels
component: core Issues re: The core compiler feature request New feature or request help wanted Extra attention is needed No Activity priority: low Will be handled, but not in the near term
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@narendasan @bowang007