Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

during training of VQA, validation is too slow. I guess it's due to trie search. how to speed up? #69

Closed
HiSultryMan opened this issue Apr 13, 2022 · 2 comments
Assignees

Comments

@HiSultryMan
Copy link

No description provided.

@yangapku yangapku self-assigned this Apr 13, 2022
@yangapku
Copy link
Member

Hi, in the current code we use all-candidate evaluation for validation during training, which is much slower than beam-search evaluation (as mentioned in the readme). You can try to disable (use a large --validate-interval) automatic validation during training and manually use evaluate.py to evaluate the checkpoint on the validation set using beam-search evaluation, which is much faster. Or moving further, you can try to move the beam-search evaluation code from eval_utils.py to replace the automatic validation code during training in the valid_step method of vqa_gen.py, which we haven't done yet.

@yangapku
Copy link
Member

@HiSultryMan Hi, we have updated the code to support beam-search validation during VQA fine-tuning, which will be much faster than the previous all-candidate validation. For more information, please refer to this PR #79 and pull the latest codebase.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants