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

Why vocabulary is divided by GPU number and how to load it? #21

Closed
Aurora-slz opened this issue Jul 5, 2022 · 3 comments
Closed

Why vocabulary is divided by GPU number and how to load it? #21

Aurora-slz opened this issue Jul 5, 2022 · 3 comments

Comments

@Aurora-slz
Copy link

When I train a pretraining model, the vocabulary is divided by the number of GPU. So I can't directly load it with origin model in downstream tasks.
How should I do?Thanks!

@duzx16
Copy link
Member

duzx16 commented Jul 6, 2022

The vocabulary size is divided by MP_SIZE (which is the model parallel size). Did you set MP_SIZE to the number of GPUs? To use the original model, MP_SIZE should be set to 1.

@SeonggwanAhn
Copy link

In addition, you can refer to this for setting MP_SIZE.

@Aurora-slz
Copy link
Author

Thanks! I used the change_mp.py to combine them into one and solve the problem.

@duzx16 duzx16 closed this as completed Jul 7, 2022
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

3 participants