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

Slow speed #2

Open
Zhentao-Liu opened this issue Jul 16, 2024 · 4 comments
Open

Slow speed #2

Zhentao-Liu opened this issue Jul 16, 2024 · 4 comments

Comments

@Zhentao-Liu
Copy link

I think it may be a little slower than original 3DGS. Have you ever tested its time efficiency?

@lzhnb
Copy link
Owner

lzhnb commented Jul 16, 2024

Since we introduced more square root and exponentiation operations, the forward and backward passes will be slower. The same is true for the inference stage, and the CUDA implementation will be slower.
But after writing it in GLSL, the fragment shader can handle this part of the operation efficiently, so we are not very slow in the Online Viewer.
I have not yet found the reason why the tile-based rendering implemented in CUDA is slower than GLSL.

@Zhentao-Liu
Copy link
Author

Thanks for your answer. Did you mean the training would be slower? And I try you code, its really much slower than the original 3DGS. The training time is very important to me. No offense.

@lzhnb
Copy link
Owner

lzhnb commented Jul 16, 2024

Yes, I have tried to speed up the code, but many of the operations are unavoidable.
For efficiency, Mip-Splatting is indeed better than ours. I'm sorry that our method cannot meet your efficiency requirements.

@Zhentao-Liu
Copy link
Author

Thanks for your guidance. Anyway, your work is valuable. Integral is more accurate than filtering.

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