Not sure about why opt_level=0,1,2 results in different outputs. Maybe TensorRT
assumes an opt_level 3 pass is always on so the correcntess without that pass
is not guaranteed, but this is just my guess.
For the performance, although again I'm not sure if this is the reason, you can
add this line before each build. This cleans the compile engine cache to avoid
incorrect measurement.
```python
relay.backend.compile_engine.get().clear()
with tvm.transform.PassContext(...):
g2, m2, p2 = relay.build(mod, tgt, params=params)
```
---
[Visit
Topic](https://discuss.tvm.apache.org/t/tensorrt-seems-ctx-sync-does-not-work-while-using-tensorrt-on-jetson-xavier-nx/9579/6)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.apache.org/email/unsubscribe/f9b941a08f655daabce08c74e1baf353b611a832d2cce3300ddff45ed76c8f09).
