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

Store all 3DGS in RAM and then move the required 3DGS to video memory #78

Open
smart4654154 opened this issue Sep 22, 2024 · 2 comments

Comments

@smart4654154
Copy link

in the parper, I find:
We update the cut every 2 frames to add details by transferring nodes to the GPU from CPU RAM, and run cleanup every 100 frames.
You put all the 3DGS in RAM, and when rendering, call the required 3DGS, then put it in the VRAM, and perform rendering.
Do I understand correctly?
image

Thank you very much.

@venite-xjc
Copy link

Hello! My understanding aligns with yours, but I didn't grasp how this paper efficiently schedules data while achieving real-time rendering. The code only demonstrates a method of loading all data into GPU memory at once. Do you have any thoughts on the implementation?

@laphisboy
Copy link

i am also very curious about this. could you point out where in the code the CPU to GPU Gaussian transferring happens, if it is implemented?

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

3 participants