Skip to content
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

Low speed on TUM/Replica dataset #17

Open
Poiw opened this issue Dec 31, 2024 · 2 comments
Open

Low speed on TUM/Replica dataset #17

Poiw opened this issue Dec 31, 2024 · 2 comments

Comments

@Poiw
Copy link

Poiw commented Dec 31, 2024

Hi,

I tried to run the pipeline on TUM and Replica dataset but it is much slower than the numbers reported in the paper. The actual speed is less than 0.5 FPS. I tested the pipeline on an RTX 4090, so it should be faster. Is there any settings I need to modify to match the numbers in the paper?

Thanks

@eriksandstroem
Copy link
Collaborator

Hi @Poiw ,
Sorry for my late reply. The reason for this traces itself back to MonoGS actually, since we reuse parts of their mapping code. It seems that running the codebase on a cluster machine is much slower than running it on a local device, as long as the local device has enough memory etc. We are still not sure why this is the case.

Did you run on a local machine or on a cluster?

@Poiw
Copy link
Author

Poiw commented Jan 5, 2025

HI @eriksandstroem ,

Thanks for the reply! I run the code on a local machine. The replica sequences are faster which achieves > 1fps, but the TUM sequence (fr1, desk) I tested is less than 0.5 FPS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants