-
Notifications
You must be signed in to change notification settings - Fork 600
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
Supplied build.sh
builds for CPU only and ignores GPU
#179
Comments
Using an environment set up using Anaconda and Python 3.9, the produced binary also uses the CPU instead of the GPU when using the "b2py t2im" command (~5s/it instead of 1s/it when using the election GUI). |
Starting to wonder whether anyone other than the @divamgupta has been able to build properly at all. been wanting to contribute for weeks now, I know it's not fun to write build documentation, but I really think it would help the community if there's an actual way to build this repository for anyone other than the original creator. I had this same issue as well as other issues I still couldn't find an answer to (from this thread #62) Just making it easy for people to build will accelerate the development exponentially. |
I have also been wanting to contribute and have succeeded in building the app a few months ago but I had to make a couple of temporary modifications to the backend for it to work. It was clearly not the way it was supposed to be built but it worked for some quick experimentation. I'd love to have official instructions to setup a development environment / proper build for DiffusionBee. I'm thinking of contributing a few bug fixes at first but I have some other things in mind (mostly small but nice UX tweaks and features) that I'm sure a lot of people would appreciate. |
Below is the steps I've executed, on a clean MacOS install with Xcode developer tools and Homebrew.
python3
refers to Python 3.10.7, downloaded from Python.org. Not using Conda/Anaconda.Snippets from output:
The final error looks to be caused by the default version of protobuf from PIP being built for x86, so I replace it with one built from source:
and re-run:
sh build.sh
This time I get a binary. But when testing the binary - by starting it in terminal and using the test prompt:
It logs out that it's using CPU, not GPU, and is ~5x slower than the provided binary in the repo - i.e. 5.5s/it instead of 1s/it.
Any ideas anyone? This is blocking many people from contributing to the project.
The text was updated successfully, but these errors were encountered: