LocalLLaMA

2249 readers

1 users here now

Community to discuss about LLaMA, the large language model created by Meta AI.

This is intended to be a replacement for r/LocalLLaMA on Reddit.

founded 1 year ago

MODERATORS

pax@sh.itjust.works

SkySyrup@sh.itjust.works

noneabove1182@sh.itjust.works

Guide on setting up a local GGML model? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by Magiwarriorx@lemmy.world to c/localllama@sh.itjust.works

11 comments fedilink hide all child comments

I've been messing around with GPTQ models with ExLlama in ooba, and have gotten 33b models @ 3k running smoothly, but was looking to try something bigger than my VRAM can hold.

However, I'm clearly doing something wrong, and the koboldcpp.exe documentation isn't clear to me. Does anyone have a good setup guide? My understanding is koboldcpp.exe is preferable for GGML, as ooba's llama.cpp doesn't support GGML at >4k context yet.

you are viewing a single comment's thread
view the rest of the comments

[–] Magiwarriorx@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

Note this is koboldcpp.exe and not KoboldAI.

The Github describes arguments to use GPU acceleration, but it is fuzzy on what the arguments do and completely neglects to mention what the values for those arguments do. I understand the --gpulayers arg, but the two ints after --useclblast are lost on me. I defaulted to "[path]\koboldcpp.exe --useclblast 0 0 --gpulayers 40", but it seems to be completely ignoring GPU acceleration, and I'm clueless where the problem lies. I figured it would be easier to ask for a guide and just start my GGML setup from scratch.

[–] actuallyacat@sh.itjust.works 2 points 1 year ago

Those are OpenCL platform and device identifiers, you can use clinfo to find out which numbers are what on your system.

Also note that if you're building kobold.cpp yourself, you need to build with LLAMA_CLBLAST=1 for OpenCL support to exist in the first place. Or LLAMA_CUBLAS for CUDA.