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

Reproducing training, recommended hardware setup #9

Closed
pvoigtlaender opened this issue Apr 7, 2022 · 2 comments
Closed

Reproducing training, recommended hardware setup #9

pvoigtlaender opened this issue Apr 7, 2022 · 2 comments

Comments

@pvoigtlaender
Copy link

pvoigtlaender commented Apr 7, 2022

Hi,

Thanks for releasing the great code!
I'm trying to reproduce the training, for now I start with the pre-trained model and just do the fine-tuning on YouTube-VOS. What is the recommended number of GPUs and what run-time should I expect?
Is the currently released code able to support multi-node training?
So far, I was able to run the YouTube-VOS training on a single machine with 4xA100 GPU and it took ~2 hours per epoch, so 12 hours in total.
Please let me know about the recommended hardware setup for the YouTube-VOS fine-tuning and also for the pre-training step (I think for this maybe not all code is released yet?).
And if I use a different number of GPUs, can I expect the same result quality, just longer run-time, or will this maybe lead to problems/worse results?

Thank you!

Best,

Paul

@wjn922
Copy link
Owner

wjn922 commented Apr 7, 2022

Hi,

Thanks for your interest.

We do not support multi-node training in the repo. If you are interested, you may refer to repo Deformable-DETR and do some modifications.

We run the finetune stage on 8 V100 GPUs with 32 memory. It is also ~2 hours per epoch.
For the pretraining stage, we run it on 32 V100 GPUs around 1~2 days. Actually, we have released the data conversion and main file for pretraining. We may provide a more detailed instruction on pretraining in the future.

As the model has been pretrained, the result would be stable. And because the evaluation is not convenient, we do not test the results for other configurations. Empirically, longer training time would lead to slightly high performance.

@pvoigtlaender
Copy link
Author

Great, thank you for the details :)
I might come back with more questions at a later point.

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