-
Notifications
You must be signed in to change notification settings - Fork 65
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
[Open-to-community] Benchmark bloomz.cpp on different hardware #4
Comments
Is it possible to run this on windows? |
Good point! Feel free to open a PR for that if you'd like @eschaffn 🚀 |
I didn't expect conversion to need 22 GiB RAM (running on Win64 native python3.11). Quantization used more ore less 10 GiB RAM running on WSL Ubuntu / gcc-9.4.0.
Executed at around 5.5 token/s on a AMD Ryzen 5 3600:
|
FreeBSD 13 on Intel i7-3770 CPU @ 3.40GHz:
|
Intel I9-13900KS Running on Windows 10 with WSL 2 Ubuntu with CUDA
After quantitization:
|
Tried on my MacBook Pro 14inch, M2 Max, 96GB memory running macOS Ventura 13.2.1!
After quantitization:
|
Hey hey,
We are working hard to help you unlock the truest potential of open-source LLMs. In order for us to build better and cater to the majority of hardware we need your help to run benchmarks with bloomz.cpp 🤗
We are looking for the following information:
You can do so by following the quickstart steps in the project's README. 💯
Ping @NouamaneTazi and @Vaibhavs10 if you have any questions! <3
Happy benchmarking! 🚀
The text was updated successfully, but these errors were encountered: