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

Evaluation takes 5 hours for one checkpoint. #11

Open
PatZhuang opened this issue Jan 18, 2021 · 1 comment
Open

Evaluation takes 5 hours for one checkpoint. #11

PatZhuang opened this issue Jan 18, 2021 · 1 comment

Comments

@PatZhuang
Copy link

PatZhuang commented Jan 18, 2021

So I trained a basic seq2seq model resulting with 15 checkpoints named ckpt.{num}.pth. I modified the NUM_PROCESSES filed to 4 and it takes about one day to train on a GTX 2080Ti graphic card (I used the headless habitat ver v0.1.5).

However, when I run the eval script, it takes about 5 hours to evaluate one checkpoint. Is this even normal?

And what is the point of evaluating all the checkpoints (and start from the earliest one) by the way?

@erikwijmans
Copy link
Collaborator

Evaluation for one checkpoint can take a long time when the model is bad, 5 hours is perhaps a bit higher than I would expect, but no dramatically higher.

The point of evaluating all is to be able to look at the curve that produces as it can be quite useful.

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