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

long time for train #13

Open
chensh1127 opened this issue May 1, 2024 · 1 comment
Open

long time for train #13

chensh1127 opened this issue May 1, 2024 · 1 comment

Comments

@chensh1127
Copy link

hey, it's a nice work. I am interested at your job. some custom datasets have been trained by your codes. However, the time for train is almost 4 hours. Is this normal?

@LingzheZhao
Copy link
Member

LingzheZhao commented May 1, 2024

Hi, the training time mostly depends on your hardware, image resolution and an important hyper-parameter densify_grad_thresh. For example, on the deblur-nerf synthetic datasets, it usually takes about 0.5 hours on my workstation (AMD Ryzen 7950X CPU + NVIDIA RTX 4090 GPU) and about 1 hour on our server (AMD Epyc 9554 CPU + NVIDIA RTX 4090 GPU).

If your training images are in high resolution, I would first suggest trying to add this argument --downscale_factor 4 after nerfstudio-data to speed up the training;

Also note that if you have a lot of training images, you may change the --eval-mode "all" to something else, like --eval-mode "interval" --eval-interval 20, to reduce the evaluation time:

ns-train bad-gaussians \
    --data path/to/custom_data \
    --vis viewer+tensorboard \
    nerfstudio-data --downscale_factor 4 --eval_mode "interval" --eval-interval 20

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