You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: we now store the traced symbolic functions from compile time in the metadata to use in the case of reexport. Also removes the need to access the real tensorrt engine during reexport
Given an input ``x = torch_tensorrt.Input(min_shape, opt_shape, max_shape, dtype)``,
52
-
Torch-TensorRT attempts to automatically set the constraints during ``torch.export`` tracing by constructing
52
+
Torch-TensorRT attempts to automatically set the constraints during ``torch.export`` tracing by constructing
53
53
`torch.export.Dim` objects with the provided dynamic dimensions accordingly. Sometimes, we might need to set additional constraints and Torchdynamo errors out if we don't specify them.
54
54
If you have to set any custom constraints to your model (by using `torch.export.Dim`), we recommend exporting your program first before compiling with Torch-TensorRT.
55
55
Please refer to this `documentation <https://pytorch.org/tutorials/intermediate/torch_export_tutorial.html#constraints-dynamic-shapes>`_ to export the Pytorch module with dynamic shapes.
@@ -78,7 +78,6 @@ Here's a simple example that exports a matmul layer with some restrictions on dy
78
78
# Run inference
79
79
trt_gm(*inputs)
80
80
81
-
82
81
Dynamic shapes using torch.compile (JIT)
83
82
------------------------------------
84
83
@@ -102,3 +101,164 @@ to avoid recompilation of TensorRT engines.
102
101
# No recompilation of TRT engines with modified batch size
0 commit comments