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

Directly converted from bfloat16 weights are 20x slower than converted from float32 ones. #516

Open
OlegJakushkin opened this issue Sep 11, 2023 · 0 comments

Comments

@OlegJakushkin
Copy link

Sounds like magic - yet:

Save model to bfloat16 in python -> run convert-h5-to-ggml passing 1 as target -> run ggml model and get 983.91 ms per token
Get q8_0 quantised model from that f16 artifact -> 21ms per token
vs
Save model to float32 -> run convert-h5-to-ggml passing 1 as target -> run ggml model 41.68 ms per token

tested on mpt model. So it is solvable by saving to float32 in torch, but why?

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

1 participant