8000
long inference time of using TensorrtExecutionProvider · Issue #97 · fabio-sim/LightGlue-ONNX · GitHub
More Web Proxy on the site http://driver.im/
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
Hi, since we can not guarantee that the same numbers of keypoints are extracted and matched, using TensorrtExecutionProvider will generate cached files for the first time and these caches will be used later for faster inference. However, when the network meets some new inputs that are not in the optimized ranges of cached files, the engine will generate new cached files and this may take more than 1 minutes. This is very dangerous as we are running the network online. Do you have any idea how we can solve this issue? I have also raised a similar issue in the ONNX repo. microsoft/onnxruntime#22822
The text was updated successfully, but these errors were encountered:
Hi, since we can not guarantee that the same numbers of keypoints are extracted and matched, using TensorrtExecutionProvider will generate cached files for the first time and these caches will be used later for faster inference. However, when the network meets some new inputs that are not in the optimized ranges of cached files, the engine will generate new cached files and this may take more than 1 minutes. This is very dangerous as we are running the network online. Do you have any idea how we can solve this issue? I have also raised a similar issue in the ONNX repo. microsoft/onnxruntime#22822
The text was updated successfully, but these errors were encountered: