-
Notifications
You must be signed in to change notification settings - Fork 61
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.
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
Runtime Analysis #108
Comments
l used Orin NX (16GB) edition. |
@Wu-ZW HI, we run on the Nvidia Jetson AGX Xavier for runtime analysis. The computing capability of Jetson AGX Xavier is better than your Orin NX. |
Sorry for my mistake. The comparison can be found here, but it is true that jeston orin nx is more powerful than AGX Xavier. |
Can you compare the average runtime of C++ and Python code? On our Jetson platform, the C++ feature extraction and matching is about 6x faster than the Python version. I think if a similar improvement can be achieved on your Jetson, we can conclude that Orin NX is actually not as good as AGX Xavier. |
parameters: |
In jeston Orin NX, the C++ feature extraction and matching is about 2x faster than the Python version. the improvement is not very obvious. |
It's strange. I am not sure whether it is also caused by the TensorRT version. We have also encountered the efficiency problem when using TensorRT 8.5 on GeForce RTX GPUs that are lower than 40 series. It is recommended to try to downgrade the TensorRT version to 8.4.1.5 if possible. |
May be similar to this issue. |
thanks a lot. I am also confused about above results. Addition, could I ask a question about how to export the PyTorch model to ONNX (int64)? I saw the scripts of convert_int32.py, is it convert INT64 to INT32 or FLOAT 32 to INT32? |
|
Yes, just run the script. |
I mean the different environments may affect the runtime. |
when I run euroc datasets, some parameters as follows: image size is set 640*480, superpoint max_keypoints is set 200,
the time of detecting and tracking feature points for one image is about 92 ms, more than 65 ms in paper. Is any parameters i need to adjust?
The text was updated successfully, but these errors were encountered: