Create some sort of serialization / deserialization functionality #40
Labels
Projects
Milestone
Comments
narendasan
added
feature request
|
That would be awesome to have proper serialization! I would also add that for large scale deployments this is a must have even for fp16. As if you have a lot of models, converting all of them on restart would be quite expensive. And in general in some systems doing tuning in production is generally undesirable. |
This was referenced May 28, 2020
frank-wei
pushed a commit
that referenced
this issue
Jun 4, 2022
Summary: Pull Request resolved: pytorch/fx2trt#40 add support for torch.nn.functional.conv_transpose3d Reviewed By: 842974287 Differential Revision: D35176171 fbshipit-source-id: 5b10fba4568ad9fb26203f3dd396e13a98bc3495
mfeliz-cruise
added a commit
to mfeliz-cruise/Torch-TensorRT
that referenced
this issue
Aug 23, 2022
Adds a heuristic to torch-trt partitioning's segmentation to avoid materializing segments until we hit a dependency of that segment. This can significantly reduce the number of segments/engines in cases where the linear traversal of torchscipt nodes would otherwise produce alternating torch and TRT segments which are not dependent on each-other Fixes # (issue) Please delete options that are not relevant and/or add your own. - 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) - This change requires a documentation update - [ ] My code follows the style guidelines of this project (You can use the linters) - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas and hacks - [ ] I have made corresponding changes to the documentation - [ ] I have added tests to verify my fix or my feature - [ ] New and existing unit tests pass locally with my changes - [ ] I have added the relevant labels to my PR in so that relevant reviewers are notified
mfeliz-cruise
added a commit
to mfeliz-cruise/Torch-TensorRT
that referenced
this issue
Oct 6, 2022
Adds a heuristic to torch-trt partitioning's segmentation to avoid materializing segments until we hit a dependency of that segment. This can significantly reduce the number of segments/engines in cases where the linear traversal of torchscipt nodes would otherwise produce alternating torch and TRT segments which are not dependent on each-other Fixes # (issue) Please delete options that are not relevant and/or add your own. - 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) - This change requires a documentation update - [ ] My code follows the style guidelines of this project (You can use the linters) - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas and hacks - [ ] I have made corresponding changes to the documentation - [ ] I have added tests to verify my fix or my feature - [ ] New and existing unit tests pass locally with my changes - [ ] I have added the relevant labels to my PR in so that relevant reviewers are notified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With INT8 about to land, would be a pain to have to calibrate from scratch every time. There should be some mechanism to save and load modules with the TRT engine included.
The text was updated successfully, but these errors were encountered: