-
Notifications
You must be signed in to change notification settings - Fork 26
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
running time for perpare.sh #9
Comments
Hi, do you modify the command the use 8 gpus? And make sure the total schedule is 1 epoch which should take about one day. |
Yes, I have already changed the GPU numbers to 8, and the total_epochs is also reset to 1 in the command.
|
@cailk totol -> total |
Alright, I'm an idiot. Thank you for the reminder~ |
BTW, I'm still wondering why this embeddings generation process produces training loss. Shouldn't only forward computation is required for this? |
@cailk I guess it's an implementation issue. Personally speaking I prefer to generating the feature in test mode. |
Hi, thanks for your great work!
I'm trying to run the first command in 'prepare.sh',
CUDA_VISIBLE_DEVICES=6,7 ./tools/dist_train.sh configs/lvis/detpro_ens_20e.py 2 --work-dir workdirs/collect_data --cfg-options model.roi_head.load_feature=False totol_epochs=1
which is used to generate the CLIP embeddings for precomputed proposals.
However, this process will take about 30 days with 8 16g-V100s. And in this issue #4, you already claim that it only takes one day. So I was wondering if I missed any details?
The text was updated successfully, but these errors were encountered: