-
|
This is ridiculous. At this point I have 4? installs, all not working for different broken reasons. Windows with the old env(which used to work, now it claims that it doesn't fit and tries to allocate System memory instead of GPU memory?!?) Trying a fresh install under WSL, maybe that helps. Nope. Also trying to use a one click installer got this beauty of messed up error: At this point, I'm just lost for words. 4 hours down the drain, just because of a git pull. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
If it's just the git pull that screwed things up, why don't you revert to a last known good commit hash and reinstall the requirements ? git checkout 071f0776ad6e7d8dab08e0d98d089c808807ab45
pip install -r requirements.txt --upgradeGood luck! |
Beta Was this translation helpful? Give feedback.
-
|
Regarding your second run, the DefaultCPUAllocator one: |
Beta Was this translation helpful? Give feedback.
Regarding your second run, the DefaultCPUAllocator one:
Before a 4-bit GPTQ model model can be loaded into the GPU memory (VRAM), it must be loaded into the main RAM first. It usually takes up about 1.5 times mode space in RAM than on disk (because reasons). Look at
alpaca-30b-4bit.pt, measure its size on disk and multiply it by 1.5 — that’s how much actual free RAM you need before python starts loading it. You might just not have this much. Happened to me before. I can’t even use 13B models with my 16G of RAM.Another thing to keep in mind when working with GPTQ models is that they cannot be split between VRAM, RAM and disk cache, so
--auto-devices,--gpu-memory,--cpu-memory,--disk flags…