2023-03-10 19:47:46 +00:00
# llama.cpp
2023-04-05 15:56:20 +00:00
![llama ](https://user-images.githubusercontent.com/1991296/230134379-7181e485-c521-4d23-a0d6-f7b3b61ba524.png )
2023-03-26 07:20:49 +00:00
2023-03-12 20:09:26 +00:00
[![Actions Status ](https://github.com/ggerganov/llama.cpp/workflows/CI/badge.svg )](https://github.com/ggerganov/llama.cpp/actions)
[![License: MIT ](https://img.shields.io/badge/license-MIT-blue.svg )](https://opensource.org/licenses/MIT)
2023-03-15 19:39:06 +00:00
Inference of [LLaMA ](https://arxiv.org/abs/2302.13971 ) model in pure C/C++
2023-03-10 19:47:46 +00:00
2023-03-14 07:43:52 +00:00
**Hot topics:**
2023-06-04 20:38:19 +00:00
- GPU support with Metal (Apple Silicon): https://github.com/ggerganov/llama.cpp/pull/1642
- High-quality 2,3,4,5,6-bit quantization: https://github.com/ggerganov/llama.cpp/pull/1684
- Multi-GPU support: https://github.com/ggerganov/llama.cpp/pull/1607
- Training LLaMA models from scratch: https://github.com/ggerganov/llama.cpp/pull/1652
- CPU threading improvements: https://github.com/ggerganov/llama.cpp/pull/1632
2023-03-14 07:43:52 +00:00
2023-05-08 16:33:30 +00:00
< details >
< summary > Table of Contents< / summary >
< ol >
< li >
< a href = "#description" > Description< / a >
< / li >
< li >
< a href = "#usage" > Usage< / a >
< ul >
< li > < a href = "#get-the-code" > Get the Code< / a > < / li >
< li > < a href = "#build" > Build< / a > < / li >
< li > < a href = "#blas-build" > BLAS Build< / a > < / li >
< li > < a href = "#prepare-data--run" > Prepare Data & Run< / a > < / li >
< li > < a href = "#memorydisk-requirements" > Memory/Disk Requirements< / a > < / li >
< li > < a href = "#quantization" > Quantization< / a > < / li >
< li > < a href = "#interactive-mode" > Interactive mode< / a > < / li >
< li > < a href = "#instruction-mode-with-alpaca" > Instruction mode with Alpaca< / a > < / li >
< li > < a href = "#using-gpt4all" > Using GPT4All< / a > < / li >
< li > < a href = "#using-pygmalion-7b--metharme-7b" > Using Pygmalion 7B & Metharme 7B< / a > < / li >
< li > < a href = "#obtaining-the-facebook-llama-original-model-and-stanford-alpaca-model-data" > Obtaining the Facebook LLaMA original model and Stanford Alpaca model data< / a > < / li >
< li > < a href = "#verifying-the-model-files" > Verifying the model files< / a > < / li >
< li > < a href = "#seminal-papers-and-background-on-the-models" > Seminal papers and background on the models< / a > < / li >
< li > < a href = "#perplexity-measuring-model-quality" > Perplexity (measuring model quality)< / a > < / li >
< li > < a href = "#android" > Android< / a > < / li >
< li > < a href = "#docker" > Docker< / a > < / li >
< / ul >
< / li >
< li > < a href = "#contributing" > Contributing< / a > < / li >
< li > < a href = "#coding-guidelines" > Coding guidelines< / a > < / li >
< li > < a href = "#docs" > Docs< / a > < / li >
< / ol >
< / details >
2023-03-10 19:47:46 +00:00
## Description
2023-04-26 20:24:42 +00:00
The main goal of `llama.cpp` is to run the LLaMA model using 4-bit integer quantization on a MacBook
2023-03-10 19:47:46 +00:00
- Plain C/C++ implementation without dependencies
2023-06-04 20:34:30 +00:00
- Apple silicon first-class citizen - optimized via ARM NEON, Accelerate and Metal frameworks
2023-05-05 14:43:36 +00:00
- AVX, AVX2 and AVX512 support for x86 architectures
2023-03-10 19:47:46 +00:00
- Mixed F16 / F32 precision
2023-05-05 14:43:36 +00:00
- 4-bit, 5-bit and 8-bit integer quantization support
2023-05-20 14:58:31 +00:00
- Supports OpenBLAS/Apple BLAS/ARM Performance Lib/ATLAS/BLIS/Intel MKL/NVHPC/ACML/SCSL/SGIMATH and [more ](https://cmake.org/cmake/help/latest/module/FindBLAS.html#blas-lapack-vendors ) in BLAS
2023-05-05 14:43:36 +00:00
- cuBLAS and CLBlast support
2023-03-10 19:47:46 +00:00
2023-04-26 20:24:42 +00:00
The original implementation of `llama.cpp` was [hacked in an evening ](https://github.com/ggerganov/llama.cpp/issues/33#issuecomment-1465108022 ).
Since then, the project has improved significantly thanks to many contributions. This project is for educational purposes and serves
as the main playground for developing new features for the [ggml ](https://github.com/ggerganov/ggml ) library.
2023-03-11 10:31:21 +00:00
2023-04-05 15:56:20 +00:00
**Supported platforms:**
2023-03-12 06:41:54 +00:00
- [X] Mac OS
- [X] Linux
2023-03-13 17:21:51 +00:00
- [X] Windows (via CMake)
2023-03-17 09:47:06 +00:00
- [X] Docker
2023-03-12 06:41:54 +00:00
2023-04-05 15:56:20 +00:00
**Supported models:**
2023-03-29 16:37:20 +00:00
2023-03-30 19:31:54 +00:00
- [X] LLaMA 🦙
2023-03-29 16:37:20 +00:00
- [X] [Alpaca ](https://github.com/ggerganov/llama.cpp#instruction-mode-with-alpaca )
- [X] [GPT4All ](https://github.com/ggerganov/llama.cpp#using-gpt4all )
2023-03-30 19:31:54 +00:00
- [X] [Chinese LLaMA / Alpaca ](https://github.com/ymcui/Chinese-LLaMA-Alpaca )
- [X] [Vigogne (French) ](https://github.com/bofenghuang/vigogne )
2023-04-05 15:56:20 +00:00
- [X] [Vicuna ](https://github.com/ggerganov/llama.cpp/discussions/643#discussioncomment-5533894 )
2023-04-10 20:41:53 +00:00
- [X] [Koala ](https://bair.berkeley.edu/blog/2023/04/03/koala/ )
2023-05-04 16:33:31 +00:00
- [X] [OpenBuddy 🐶 (Multilingual) ](https://github.com/OpenBuddy/OpenBuddy )
2023-05-08 16:33:30 +00:00
- [X] [Pygmalion 7B / Metharme 7B ](#using-pygmalion-7b--metharme-7b )
2023-05-19 17:16:30 +00:00
- [X] [WizardLM ](https://github.com/nlpxucan/WizardLM )
2023-04-05 15:56:20 +00:00
**Bindings:**
- Python: [abetlen/llama-cpp-python ](https://github.com/abetlen/llama-cpp-python )
- Go: [go-skynet/go-llama.cpp ](https://github.com/go-skynet/go-llama.cpp )
2023-04-13 13:54:27 +00:00
- Node.js: [hlhr202/llama-node ](https://github.com/hlhr202/llama-node )
2023-04-17 19:34:35 +00:00
- Ruby: [yoshoku/llama_cpp.rb ](https://github.com/yoshoku/llama_cpp.rb )
2023-05-12 05:39:40 +00:00
- C#/.NET: [SciSharp/LLamaSharp ](https://github.com/SciSharp/LLamaSharp )
2023-04-05 15:56:20 +00:00
**UI:**
- [nat/openplayground ](https://github.com/nat/openplayground )
- [oobabooga/text-generation-webui ](https://github.com/oobabooga/text-generation-webui )
2023-03-29 16:37:20 +00:00
2023-03-11 10:31:21 +00:00
---
2023-03-10 19:47:46 +00:00
2023-03-11 08:47:09 +00:00
Here is a typical run using LLaMA-7B:
2023-03-10 19:47:46 +00:00
```java
2023-03-17 17:47:35 +00:00
make -j & & ./main -m ./models/7B/ggml-model-q4_0.bin -p "Building a website can be done in 10 simple steps:" -n 512
2023-03-11 08:47:09 +00:00
I llama.cpp build info:
2023-03-10 19:47:46 +00:00
I UNAME_S: Darwin
I UNAME_P: arm
I UNAME_M: arm64
I CFLAGS: -I. -O3 -DNDEBUG -std=c11 -fPIC -pthread -DGGML_USE_ACCELERATE
I CXXFLAGS: -I. -I./examples -O3 -DNDEBUG -std=c++11 -fPIC -pthread
I LDFLAGS: -framework Accelerate
I CC: Apple clang version 14.0.0 (clang-1400.0.29.202)
I CXX: Apple clang version 14.0.0 (clang-1400.0.29.202)
2023-03-10 22:09:19 +00:00
make: Nothing to be done for `default'.
main: seed = 1678486056
2023-03-11 08:47:09 +00:00
llama_model_load: loading model from './models/7B/ggml-model-q4_0.bin' - please wait ...
2023-03-10 19:47:46 +00:00
llama_model_load: n_vocab = 32000
llama_model_load: n_ctx = 512
llama_model_load: n_embd = 4096
llama_model_load: n_mult = 256
llama_model_load: n_head = 32
llama_model_load: n_layer = 32
2023-03-10 22:09:19 +00:00
llama_model_load: n_rot = 128
2023-03-10 19:47:46 +00:00
llama_model_load: f16 = 2
llama_model_load: n_ff = 11008
llama_model_load: ggml ctx size = 4529.34 MB
llama_model_load: memory_size = 512.00 MB, n_mem = 16384
llama_model_load: .................................... done
llama_model_load: model size = 4017.27 MB / num tensors = 291
2023-03-10 22:09:19 +00:00
main: prompt: 'Building a website can be done in 10 simple steps:'
main: number of tokens in prompt = 15
2023-03-10 19:47:46 +00:00
1 -> ''
2023-03-10 22:09:19 +00:00
8893 -> 'Build'
292 -> 'ing'
263 -> ' a'
4700 -> ' website'
508 -> ' can'
367 -> ' be'
2309 -> ' done'
297 -> ' in'
29871 -> ' '
29896 -> '1'
29900 -> '0'
2560 -> ' simple'
6576 -> ' steps'
29901 -> ':'
2023-03-10 19:47:46 +00:00
sampling parameters: temp = 0.800000, top_k = 40, top_p = 0.950000
2023-03-10 22:09:19 +00:00
Building a website can be done in 10 simple steps:
1) Select a domain name and web hosting plan
2) Complete a sitemap
3) List your products
4) Write product descriptions
5) Create a user account
6) Build the template
7) Start building the website
8) Advertise the website
9) Provide email support
10) Submit the website to search engines
A website is a collection of web pages that are formatted with HTML. HTML is the code that defines what the website looks like and how it behaves.
The HTML code is formatted into a template or a format. Once this is done, it is displayed on the user's browser.
The web pages are stored in a web server. The web server is also called a host. When the website is accessed, it is retrieved from the server and displayed on the user's computer.
A website is known as a website when it is hosted. This means that it is displayed on a host. The host is usually a web server.
A website can be displayed on different browsers. The browsers are basically the software that renders the website on the user's screen.
A website can also be viewed on different devices such as desktops, tablets and smartphones.
Hence, to have a website displayed on a browser, the website must be hosted.
A domain name is an address of a website. It is the name of the website.
The website is known as a website when it is hosted. This means that it is displayed on a host. The host is usually a web server.
A website can be displayed on different browsers. The browsers are basically the software that renders the website on the user’ s screen.
A website can also be viewed on different devices such as desktops, tablets and smartphones. Hence, to have a website displayed on a browser, the website must be hosted.
A domain name is an address of a website. It is the name of the website.
A website is an address of a website. It is a collection of web pages that are formatted with HTML. HTML is the code that defines what the website looks like and how it behaves.
The HTML code is formatted into a template or a format. Once this is done, it is displayed on the user’ s browser.
A website is known as a website when it is hosted
2023-03-10 19:47:46 +00:00
main: mem per token = 14434244 bytes
2023-03-10 22:09:19 +00:00
main: load time = 1332.48 ms
main: sample time = 1081.40 ms
main: predict time = 31378.77 ms / 61.41 ms per token
main: total time = 34036.74 ms
2023-03-10 19:47:46 +00:00
```
2023-03-10 22:51:46 +00:00
And here is another demo of running both LLaMA-7B and [whisper.cpp ](https://github.com/ggerganov/whisper.cpp ) on a single M1 Pro MacBook:
https://user-images.githubusercontent.com/1991296/224442907-7693d4be-acaa-4e01-8b4f-add84093ffff.mp4
2023-03-10 19:47:46 +00:00
## Usage
2023-04-19 19:52:14 +00:00
Here are the steps for the LLaMA-7B model.
2023-04-13 13:43:22 +00:00
### Get the Code
2023-03-11 08:47:09 +00:00
2023-03-10 19:47:46 +00:00
```bash
git clone https://github.com/ggerganov/llama.cpp
cd llama.cpp
2023-04-13 13:43:22 +00:00
```
### Build
2023-04-26 20:03:03 +00:00
In order to build llama.cpp you have three different options.
2023-04-13 13:43:22 +00:00
2023-04-26 20:03:03 +00:00
- Using `make` :
- On Linux or MacOS:
2023-04-13 13:43:22 +00:00
2023-04-26 20:03:03 +00:00
```bash
make
```
- On Windows:
2023-04-28 14:22:48 +00:00
1. Download the latest fortran version of [w64devkit ](https://github.com/skeeto/w64devkit/releases ).
2023-04-26 20:03:03 +00:00
2. Extract `w64devkit` on your pc.
3. Run `w64devkit.exe` .
4. Use the `cd` command to reach the `llama.cpp` folder.
5. From here you can run:
```bash
make
```
2023-03-10 19:47:46 +00:00
2023-04-26 20:03:03 +00:00
- Using `CMake` :
2023-04-05 14:36:12 +00:00
2023-04-13 13:43:22 +00:00
```bash
mkdir build
cd build
cmake ..
cmake --build . --config Release
```
2023-04-26 20:03:03 +00:00
- Using `Zig` :
2023-04-13 13:43:22 +00:00
```bash
zig build -Drelease-fast
```
2023-06-04 20:34:30 +00:00
### Metal Build
Using Metal allows the computation to be executed on the GPU for Apple devices:
- Using `make` :
```bash
LLAMA_METAL=1 make
```
- Using `CMake` :
```bash
mkdir build-metal
cd build-metal
cmake -DLLAMA_METAL=ON ..
cmake --build . --config Release
```
When built with Metal support, you can enable GPU inference with the `--gpu-layers|-ngl` command-line argument.
Any value larger than 0 will offload the computation to the GPU. For example:
```bash
./main -m ./models/7B/ggml-model-q4_0.bin -n 128 -ngl 1
```
2023-04-26 20:03:03 +00:00
### BLAS Build
Building the program with BLAS support may lead to some performance improvements in prompt processing using batch sizes higher than 32 (the default is 512). BLAS doesn't affect the normal generation performance. There are currently three different implementations of it:
2023-06-05 20:32:36 +00:00
- #### Accelerate Framework:
2023-04-26 20:03:03 +00:00
This is only available on Mac PCs and it's enabled by default. You can just build using the normal instructions.
2023-06-05 20:32:36 +00:00
- #### OpenBLAS:
2023-04-26 20:03:03 +00:00
This provides BLAS acceleration using only the CPU. Make sure to have OpenBLAS installed on your machine.
- Using `make` :
- On Linux:
```bash
make LLAMA_OPENBLAS=1
```
- On Windows:
1. Download the latest fortran version of [w64devkit ](https://github.com/skeeto/w64devkit/releases ).
2. Download the latest version of [OpenBLAS for Windows ](https://github.com/xianyi/OpenBLAS/releases ).
3. Extract `w64devkit` on your pc.
4. From the OpenBLAS zip that you just downloaded copy `libopenblas.a` , located inside the `lib` folder, inside `w64devkit\x86_64-w64-mingw32\lib` .
5. From the same OpenBLAS zip copy the content of the `include` folder inside `w64devkit\x86_64-w64-mingw32\include` .
6. Run `w64devkit.exe` .
7. Use the `cd` command to reach the `llama.cpp` folder.
8. From here you can run:
```bash
make LLAMA_OPENBLAS=1
```
- Using `CMake` on Linux:
```bash
mkdir build
cd build
2023-05-20 14:58:31 +00:00
cmake .. -DLLAMA_BLAS=ON -DLLAMA_BLAS_VENDOR=OpenBLAS
2023-04-26 20:03:03 +00:00
cmake --build . --config Release
```
2023-06-05 20:32:36 +00:00
- #### BLIS
2023-05-20 14:58:31 +00:00
Check [BLIS.md ](BLIS.md ) for more information.
2023-06-05 20:32:36 +00:00
- #### Intel MKL
2023-05-20 14:58:31 +00:00
By default, `LLAMA_BLAS_VENDOR` is set to `Generic` , so if you already sourced intel environment script and assign `-DLLAMA_BLAS=ON` in cmake, the mkl version of Blas will automatically been selected. You may also specify it by:
```bash
mkdir build
cd build
cmake .. -DLLAMA_BLAS=ON -DLLAMA_BLAS_VENDOR=Intel10_64lp -DCMAKE_C_COMPILER=icx -DCMAKE_CXX_COMPILER=icpx
2023-06-05 20:28:37 +00:00
cmake --build . --config Release
2023-05-20 14:58:31 +00:00
```
2023-06-05 20:32:36 +00:00
- #### cuBLAS
2023-04-26 20:03:03 +00:00
This provides BLAS acceleration using the CUDA cores of your Nvidia GPU. Make sure to have the CUDA toolkit installed. You can download it from your Linux distro's package manager or from here: [CUDA Toolkit ](https://developer.nvidia.com/cuda-downloads ).
- Using `make` :
```bash
make LLAMA_CUBLAS=1
```
- Using `CMake` :
```bash
mkdir build
cd build
cmake .. -DLLAMA_CUBLAS=ON
cmake --build . --config Release
```
2023-05-27 15:47:55 +00:00
Note: Because llama.cpp uses multiple CUDA streams for matrix multiplication results [are not guaranteed to be reproducible ](https://docs.nvidia.com/cuda/cublas/index.html#results-reproducibility ). If you need reproducibility, set `GGML_CUDA_MAX_STREAMS` in the file `ggml-cuda.cu` to 1.
2023-04-26 20:03:03 +00:00
2023-06-03 13:35:20 +00:00
The environment variable [`CUDA_VISIBLE_DEVICES` ](https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#env-vars ) can be used to specify which GPU(s) will be used.
2023-06-05 20:32:36 +00:00
- #### CLBlast
2023-05-27 15:47:55 +00:00
OpenCL acceleration is provided by the matrix multiplication kernels from the [CLBlast ](https://github.com/CNugteren/CLBlast ) project and custom kernels for ggml that can generate tokens on the GPU.
You will need the [OpenCL SDK ](https://github.com/KhronosGroup/OpenCL-SDK ).
- For Ubuntu or Debian, the packages `opencl-headers` , `ocl-icd` may be needed.
- < details >
< summary > Installing the OpenCL SDK from source< / summary >
```sh
git clone --recurse-submodules https://github.com/KhronosGroup/OpenCL-SDK.git
mkdir OpenCL-SDK/build
cd OpenCL-SDK/build
cmake .. -DBUILD_DOCS=OFF \
-DBUILD_EXAMPLES=OFF \
-DBUILD_TESTING=OFF \
-DOPENCL_SDK_BUILD_SAMPLES=OFF \
-DOPENCL_SDK_TEST_SAMPLES=OFF
cmake --build . --config Release
cmake --install . --prefix /some/path
```
< / details >
Installing CLBlast: it may be found in your operating system's packages.
- < details >
< summary > If not, then installing from source:< / summary >
```sh
git clone https://github.com/CNugteren/CLBlast.git
mkdir CLBlast/build
cd CLBLast/build
cmake .. -DBUILD_SHARED_LIBS=OFF -DTUNERS=OFF
cmake --build . --config Release
cmake --install . --prefix /some/path
```
2023-06-03 13:35:20 +00:00
Where `/some/path` is where the built library will be installed (default is `/usr/local` ).
2023-05-27 15:47:55 +00:00
< / details >
Building:
- Build with make:
```sh
make LLAMA_CLBLAST=1
```
- CMake:
```sh
mkdir build
cd build
cmake .. -DLLAMA_CLBLAST=ON -DCLBlast_dir=/some/path
cmake --build . --config Release
```
Running:
2023-06-04 20:34:30 +00:00
The CLBlast build supports `--gpu-layers|-ngl` like the CUDA version does.
2023-05-27 15:47:55 +00:00
To select the correct platform (driver) and device (GPU), you can use the environment variables `GGML_OPENCL_PLATFORM` and `GGML_OPENCL_DEVICE` .
The selection can be a number (starting from 0) or a text string to search:
```sh
GGML_OPENCL_PLATFORM=1 ./main ...
GGML_OPENCL_DEVICE=2 ./main ...
GGML_OPENCL_PLATFORM=Intel ./main ...
GGML_OPENCL_PLATFORM=AMD GGML_OPENCL_DEVICE=1 ./main ...
```
The default behavior is to find the first GPU device, but when it is an integrated GPU on a laptop, for instance, the selectors are useful.
Using the variables it is possible to select a CPU-based driver as well, if so desired.
You can get a list of platforms and devices from the `clinfo -l` command, etc.
2023-05-08 00:42:01 +00:00
2023-04-13 13:43:22 +00:00
### Prepare Data & Run
```bash
2023-03-10 19:47:46 +00:00
# obtain the original LLaMA model weights and place them in ./models
ls ./models
65B 30B 13B 7B tokenizer_checklist.chk tokenizer.model
2023-03-11 05:47:26 +00:00
# install Python dependencies
py : new conversion script (#545)
Current status: Working, except for the latest GPTQ-for-LLaMa format
that includes `g_idx`. This turns out to require changes to GGML, so
for now it only works if you use the `--outtype` option to dequantize it
back to f16 (which is pointless except for debugging).
I also included some cleanup for the C++ code.
This script is meant to replace all the existing conversion scripts
(including the ones that convert from older GGML formats), while also
adding support for some new formats. Specifically, I've tested with:
- [x] `LLaMA` (original)
- [x] `llama-65b-4bit`
- [x] `alpaca-native`
- [x] `alpaca-native-4bit`
- [x] LLaMA converted to 'transformers' format using
`convert_llama_weights_to_hf.py`
- [x] `alpaca-native` quantized with `--true-sequential --act-order
--groupsize 128` (dequantized only)
- [x] same as above plus `--save_safetensors`
- [x] GPT4All
- [x] stock unversioned ggml
- [x] ggmh
There's enough overlap in the logic needed to handle these different
cases that it seemed best to move to a single script.
I haven't tried this with Alpaca-LoRA because I don't know where to find
it.
Useful features:
- Uses multiple threads for a speedup in some cases (though the Python
GIL limits the gain, and sometimes it's disk-bound anyway).
- Combines split models into a single file (both the intra-tensor split
of the original and the inter-tensor split of 'transformers' format
files). Single files are more convenient to work with and more
friendly to future changes to use memory mapping on the C++ side. To
accomplish this without increasing memory requirements, it has some
custom loading code which avoids loading whole input files into memory
at once.
- Because of the custom loading code, it no longer depends in PyTorch,
which might make installing dependencies slightly easier or faster...
although it still depends on NumPy and sentencepiece, so I don't know
if there's any meaningful difference. In any case, I also added a
requirements.txt file to lock the dependency versions in case of any
future breaking changes.
- Type annotations checked with mypy.
- Some attempts to be extra user-friendly:
- The script tries to be forgiving with arguments, e.g. you can
specify either the model file itself or the directory containing
it.
- The script doesn't depend on config.json / params.json, just in
case the user downloaded files individually and doesn't have those
handy. But you still need tokenizer.model and, for Alpaca,
added_tokens.json.
- The script tries to give a helpful error message if
added_tokens.json is missing.
2023-04-14 07:03:03 +00:00
python3 -m pip install -r requirements.txt
2023-03-11 05:47:26 +00:00
2023-03-10 19:47:46 +00:00
# convert the 7B model to ggml FP16 format
py : new conversion script (#545)
Current status: Working, except for the latest GPTQ-for-LLaMa format
that includes `g_idx`. This turns out to require changes to GGML, so
for now it only works if you use the `--outtype` option to dequantize it
back to f16 (which is pointless except for debugging).
I also included some cleanup for the C++ code.
This script is meant to replace all the existing conversion scripts
(including the ones that convert from older GGML formats), while also
adding support for some new formats. Specifically, I've tested with:
- [x] `LLaMA` (original)
- [x] `llama-65b-4bit`
- [x] `alpaca-native`
- [x] `alpaca-native-4bit`
- [x] LLaMA converted to 'transformers' format using
`convert_llama_weights_to_hf.py`
- [x] `alpaca-native` quantized with `--true-sequential --act-order
--groupsize 128` (dequantized only)
- [x] same as above plus `--save_safetensors`
- [x] GPT4All
- [x] stock unversioned ggml
- [x] ggmh
There's enough overlap in the logic needed to handle these different
cases that it seemed best to move to a single script.
I haven't tried this with Alpaca-LoRA because I don't know where to find
it.
Useful features:
- Uses multiple threads for a speedup in some cases (though the Python
GIL limits the gain, and sometimes it's disk-bound anyway).
- Combines split models into a single file (both the intra-tensor split
of the original and the inter-tensor split of 'transformers' format
files). Single files are more convenient to work with and more
friendly to future changes to use memory mapping on the C++ side. To
accomplish this without increasing memory requirements, it has some
custom loading code which avoids loading whole input files into memory
at once.
- Because of the custom loading code, it no longer depends in PyTorch,
which might make installing dependencies slightly easier or faster...
although it still depends on NumPy and sentencepiece, so I don't know
if there's any meaningful difference. In any case, I also added a
requirements.txt file to lock the dependency versions in case of any
future breaking changes.
- Type annotations checked with mypy.
- Some attempts to be extra user-friendly:
- The script tries to be forgiving with arguments, e.g. you can
specify either the model file itself or the directory containing
it.
- The script doesn't depend on config.json / params.json, just in
case the user downloaded files individually and doesn't have those
handy. But you still need tokenizer.model and, for Alpaca,
added_tokens.json.
- The script tries to give a helpful error message if
added_tokens.json is missing.
2023-04-14 07:03:03 +00:00
python3 convert.py models/7B/
2023-03-10 19:47:46 +00:00
2023-04-26 16:43:27 +00:00
# quantize the model to 4-bits (using q4_0 method)
./quantize ./models/7B/ggml-model-f16.bin ./models/7B/ggml-model-q4_0.bin q4_0
2023-03-10 19:47:46 +00:00
# run the inference
2023-03-17 17:47:35 +00:00
./main -m ./models/7B/ggml-model-q4_0.bin -n 128
2023-03-10 19:47:46 +00:00
```
2023-03-11 08:47:09 +00:00
When running the larger models, make sure you have enough disk space to store all the intermediate files.
2023-03-18 20:58:46 +00:00
### Memory/Disk Requirements
2023-04-19 19:52:14 +00:00
As the models are currently fully loaded into memory, you will need adequate disk space to save them and sufficient RAM to load them. At the moment, memory and disk requirements are the same.
2023-03-18 20:58:46 +00:00
2023-04-28 23:10:43 +00:00
| Model | Original size | Quantized size (4-bit) |
|------:|--------------:|-----------------------:|
| 7B | 13 GB | 3.9 GB |
| 13B | 24 GB | 7.8 GB |
| 30B | 60 GB | 19.5 GB |
| 65B | 120 GB | 38.5 GB |
2023-03-13 16:15:20 +00:00
2023-04-26 20:24:42 +00:00
### Quantization
Several quantization methods are supported. They differ in the resulting model disk size and inference speed.
2023-05-11 21:23:08 +00:00
| Model | Measure | F16 | Q4_0 | Q4_1 | Q5_0 | Q5_1 | Q8_0 |
|------:|--------------|-------:|-------:|-------:|-------:|-------:|-------:|
2023-05-19 19:17:18 +00:00
| 7B | perplexity | 5.9066 | 6.1565 | 6.0912 | 5.9862 | 5.9481 | 5.9070 |
| 7B | file size | 13.0G | 3.5G | 3.9G | 4.3G | 4.7G | 6.7G |
| 7B | ms/tok @ 4th | 127 | 55 | 54 | 76 | 83 | 72 |
| 7B | ms/tok @ 8th | 122 | 43 | 45 | 52 | 56 | 67 |
| 7B | bits/weight | 16.0 | 4.5 | 5.0 | 5.5 | 6.0 | 8.5 |
| 13B | perplexity | 5.2543 | 5.3860 | 5.3608 | 5.2856 | 5.2706 | 5.2548 |
| 13B | file size | 25.0G | 6.8G | 7.6G | 8.3G | 9.1G | 13G |
| 13B | ms/tok @ 4th | - | 103 | 105 | 148 | 160 | 131 |
| 13B | ms/tok @ 8th | - | 73 | 82 | 98 | 105 | 128 |
| 13B | bits/weight | 16.0 | 4.5 | 5.0 | 5.5 | 6.0 | 8.5 |
2023-04-26 20:24:42 +00:00
2023-05-08 14:41:54 +00:00
### Perplexity (measuring model quality)
You can use the `perplexity` example to measure perplexity over a given prompt (lower perplexity is better).
For more information, see [https://huggingface.co/docs/transformers/perplexity ](https://huggingface.co/docs/transformers/perplexity ).
The perplexity measurements in table above are done against the `wikitext2` test dataset (https://paperswithcode.com/dataset/wikitext-2), with context length of 512.
The time per token is measured on a MacBook M1 Pro 32GB RAM using 4 and 8 threads.
2023-03-12 21:13:28 +00:00
### Interactive mode
If you want a more ChatGPT-like experience, you can run in interactive mode by passing `-i` as a parameter.
2023-04-19 19:52:14 +00:00
In this mode, you can always interrupt generation by pressing Ctrl+C and entering one or more lines of text, which will be converted into tokens and appended to the current context. You can also specify a *reverse prompt* with the parameter `-r "reverse prompt string"` . This will result in user input being prompted whenever the exact tokens of the reverse prompt string are encountered in the generation. A typical use is to use a prompt that makes LLaMa emulate a chat between multiple users, say Alice and Bob, and pass `-r "Alice:"` .
2023-03-12 21:13:28 +00:00
2023-04-19 19:52:14 +00:00
Here is an example of a few-shot interaction, invoked with the command
2023-03-21 16:10:32 +00:00
```bash
2023-04-19 19:52:14 +00:00
# default arguments using a 7B model
2023-03-25 18:36:52 +00:00
./examples/chat.sh
2023-04-19 19:52:14 +00:00
# advanced chat with a 13B model
2023-03-25 18:36:52 +00:00
./examples/chat-13B.sh
2023-03-12 21:39:01 +00:00
2023-04-19 19:52:14 +00:00
# custom arguments using a 13B model
2023-03-21 16:09:37 +00:00
./main -m ./models/13B/ggml-model-q4_0.bin -n 256 --repeat_penalty 1.0 --color -i -r "User:" -f prompts/chat-with-bob.txt
2023-03-12 21:13:28 +00:00
```
2023-03-21 16:10:32 +00:00
2023-04-24 15:45:32 +00:00
Note the use of `--color` to distinguish between user input and generated text. Other parameters are explained in more detail in the [README ](examples/main/README.md ) for the `main` example program.
2023-03-12 21:13:28 +00:00
2023-03-12 21:39:01 +00:00
![image ](https://user-images.githubusercontent.com/1991296/224575029-2af3c7dc-5a65-4f64-a6bb-517a532aea38.png )
2023-03-12 21:13:28 +00:00
2023-05-24 06:24:01 +00:00
### Persistent Interaction
The prompt, user inputs, and model generations can be saved and resumed across calls to `./main` by leveraging `--prompt-cache` and `--prompt-cache-all` . The `./examples/chat-persistent.sh` script demonstrates this with support for long-running, resumable chat sessions. To use this example, you must provide a file to cache the initial chat prompt and a directory to save the chat session, and may optionally provide the same variables as `chat-13B.sh` . The same prompt cache can be reused for new chat sessions. Note that both prompt cache and chat directory are tied to the initial prompt (`PROMPT_TEMPLATE`) and the model file.
```bash
# Start a new chat
PROMPT_CACHE_FILE=chat.prompt.bin CHAT_SAVE_DIR=./chat/default ./examples/chat-persistent.sh
# Resume that chat
PROMPT_CACHE_FILE=chat.prompt.bin CHAT_SAVE_DIR=./chat/default ./examples/chat-persistent.sh
# Start a different chat with the same prompt/model
PROMPT_CACHE_FILE=chat.prompt.bin CHAT_SAVE_DIR=./chat/another ./examples/chat-persistent.sh
# Different prompt cache for different prompt/model
PROMPT_TEMPLATE=./prompts/chat-with-bob.txt PROMPT_CACHE_FILE=bob.prompt.bin \
CHAT_SAVE_DIR=./chat/bob ./examples/chat-persistent.sh
```
2023-03-19 16:49:50 +00:00
### Instruction mode with Alpaca
2023-03-23 11:30:40 +00:00
1. First, download the `ggml` Alpaca model into the `./models` folder
2. Run the `main` tool like this:
2023-03-19 16:49:50 +00:00
```
2023-03-25 18:36:52 +00:00
./examples/alpaca.sh
2023-03-19 16:49:50 +00:00
```
Sample run:
```
== Running in interactive mode. ==
- Press Ctrl+C to interject at any time.
- Press Return to return control to LLaMa.
- If you want to submit another line, end your input in '\'.
Below is an instruction that describes a task. Write a response that appropriately completes the request.
> How many letters are there in the English alphabet?
There 26 letters in the English Alphabet
> What is the most common way of transportation in Amsterdam?
The majority (54%) are using public transit. This includes buses, trams and metros with over 100 lines throughout the city which make it very accessible for tourists to navigate around town as well as locals who commute by tram or metro on a daily basis
2023-03-21 15:59:16 +00:00
> List 5 words that start with "ca".
2023-03-19 16:49:50 +00:00
cadaver, cauliflower, cabbage (vegetable), catalpa (tree) and Cailleach.
2023-04-11 19:45:44 +00:00
>
2023-03-19 16:49:50 +00:00
```
2023-03-29 16:37:20 +00:00
### Using [GPT4All](https://github.com/nomic-ai/gpt4all)
2023-04-23 08:21:26 +00:00
- Obtain the `tokenizer.model` file from LLaMA model and put it to `models`
- Obtain the `added_tokens.json` file from Alpaca model and put it to `models`
- Obtain the `gpt4all-lora-quantized.bin` file from GPT4All model and put it to `models/gpt4all-7B`
- It is distributed in the old `ggml` format which is now obsoleted
- You have to convert it to the new format using `convert.py` :
```bash
python3 convert.py models/gpt4all-7B/gpt4all-lora-quantized.bin
```
- You can now use the newly generated `models/gpt4all-7B/ggml-model-q4_0.bin` model in exactly the same way as all other models
- The newer GPT4All-J model is not yet supported!
2023-03-29 16:37:20 +00:00
2023-05-08 16:33:30 +00:00
### Using Pygmalion 7B & Metharme 7B
- Obtain the [LLaMA weights ](#obtaining-the-facebook-llama-original-model-and-stanford-alpaca-model-data )
- Obtain the [Pygmalion 7B ](https://huggingface.co/PygmalionAI/pygmalion-7b/ ) or [Metharme 7B ](https://huggingface.co/PygmalionAI/metharme-7b ) XOR encoded weights
- Convert the LLaMA model with [the latest HF convert script ](https://github.com/huggingface/transformers/blob/main/src/transformers/models/llama/convert_llama_weights_to_hf.py )
- Merge the XOR files with the converted LLaMA weights by running the [xor_codec ](https://huggingface.co/PygmalionAI/pygmalion-7b/blob/main/xor_codec.py ) script
- Convert to `ggml` format using the `convert.py` script in this repo:
```bash
python3 convert.py pygmalion-7b/ --outtype q4_1
```
> The Pygmalion 7B & Metharme 7B weights are saved in [bfloat16](https://en.wikipedia.org/wiki/Bfloat16_floating-point_format) precision. If you wish to convert to `ggml` without quantizating, please specify the `--outtype` as `f32` instead of `f16`.
2023-05-03 15:31:28 +00:00
### Obtaining the Facebook LLaMA original model and Stanford Alpaca model data
2023-03-20 20:14:06 +00:00
2023-04-19 19:52:14 +00:00
- **Under no circumstances should IPFS, magnet links, or any other links to model downloads be shared anywhere in this repository, including in issues, discussions, or pull requests. They will be immediately deleted.**
2023-04-11 19:45:44 +00:00
- The LLaMA models are officially distributed by Facebook and will **never** be provided through this repository.
2023-03-24 15:23:09 +00:00
- Refer to [Facebook's LLaMA repository ](https://github.com/facebookresearch/llama/pull/73/files ) if you need to request access to the model data.
2023-03-20 20:14:06 +00:00
2023-05-03 15:31:28 +00:00
### Verifying the model files
2023-03-20 20:14:06 +00:00
2023-05-03 15:31:28 +00:00
Please verify the [sha256 checksums ](SHA256SUMS ) of all downloaded model files to confirm that you have the correct model data files before creating an issue relating to your model files.
- The following python script will verify if you have all possible latest files in your self-installed `./models` subdirectory:
2023-03-20 20:14:06 +00:00
2023-05-03 15:31:28 +00:00
```bash
# run the verification script
python3 .\scripts\verify-checksum-models.py
```
- On linux or macOS it is also possible to run the following commands to verify if you have all possible latest files in your self-installed `./models` subdirectory:
2023-05-03 17:09:42 +00:00
- On Linux: `sha256sum --ignore-missing -c SHA256SUMS`
2023-05-03 15:31:28 +00:00
- on macOS: `shasum -a 256 --ignore-missing -c SHA256SUMS`
### Seminal papers and background on the models
2023-03-20 20:14:06 +00:00
2023-05-03 15:31:28 +00:00
If your issue is with model generation quality, then please at least scan the following links and papers to understand the limitations of LLaMA models. This is especially important when choosing an appropriate model size and appreciating both the significant and subtle differences between LLaMA models and ChatGPT:
2023-04-19 19:52:14 +00:00
- LLaMA:
2023-05-03 15:31:28 +00:00
- [Introducing LLaMA: A foundational, 65-billion-parameter large language model ](https://ai.facebook.com/blog/large-language-model-llama-meta-ai/ )
- [LLaMA: Open and Efficient Foundation Language Models ](https://arxiv.org/abs/2302.13971 )
2023-04-19 19:52:14 +00:00
- GPT-3
2023-05-03 15:31:28 +00:00
- [Language Models are Few-Shot Learners ](https://arxiv.org/abs/2005.14165 )
2023-04-19 19:52:14 +00:00
- GPT-3.5 / InstructGPT / ChatGPT:
2023-05-03 15:31:28 +00:00
- [Aligning language models to follow instructions ](https://openai.com/research/instruction-following )
- [Training language models to follow instructions with human feedback ](https://arxiv.org/abs/2203.02155 )
2023-04-11 19:45:44 +00:00
2023-03-22 15:53:54 +00:00
#### How to run
1. Download/extract: https://s3.amazonaws.com/research.metamind.io/wikitext/wikitext-2-raw-v1.zip?ref=salesforce-research
2023-03-26 13:14:01 +00:00
2. Run `./perplexity -m models/7B/ggml-model-q4_0.bin -f wiki.test.raw`
2023-03-22 15:53:54 +00:00
3. Output:
```
2023-03-26 13:14:01 +00:00
perplexity : calculating perplexity over 655 chunks
2023-03-22 15:53:54 +00:00
24.43 seconds per pass - ETA 4.45 hours
[1]4.5970,[2]5.1807,[3]6.0382,...
```
And after 4.45 hours, you will have the final perplexity.
2023-03-14 13:30:08 +00:00
### Android
2023-04-01 14:57:30 +00:00
You can easily run `llama.cpp` on Android device with [termux ](https://termux.dev/ ).
2023-03-14 13:30:08 +00:00
First, obtain the [Android NDK ](https://developer.android.com/ndk ) and then build with CMake:
```
$ mkdir build-android
$ cd build-android
$ export NDK=< your_ndk_directory >
$ cmake -DCMAKE_TOOLCHAIN_FILE=$NDK/build/cmake/android.toolchain.cmake -DANDROID_ABI=arm64-v8a -DANDROID_PLATFORM=android-23 -DCMAKE_C_FLAGS=-march=armv8.4a+dotprod ..
$ make
```
2023-04-01 14:57:30 +00:00
Install [termux ](https://termux.dev/ ) on your device and run `termux-setup-storage` to get access to your SD card.
2023-03-14 13:30:08 +00:00
Finally, copy the `llama` binary and the model files to your device storage. Here is a demo of an interactive session running on Pixel 5 phone:
https://user-images.githubusercontent.com/271616/225014776-1d567049-ad71-4ef2-b050-55b0b3b9274c.mp4
2023-03-17 09:47:06 +00:00
### Docker
#### Prerequisites
* Docker must be installed and running on your system.
2023-04-19 19:52:14 +00:00
* Create a folder to store big models & intermediate files (ex. /llama/models)
2023-03-17 09:47:06 +00:00
#### Images
We have two Docker images available for this project:
1. `ghcr.io/ggerganov/llama.cpp:full` : This image includes both the main executable file and the tools to convert LLaMA models into ggml and convert into 4-bit quantization.
2. `ghcr.io/ggerganov/llama.cpp:light` : This image only includes the main executable file.
#### Usage
The easiest way to download the models, convert them to ggml and optimize them is with the --all-in-one command which includes the full docker image.
2023-04-06 06:56:58 +00:00
Replace `/path/to/models` below with the actual path where you downloaded the models.
2023-04-19 19:52:14 +00:00
```bash
2023-04-06 06:56:58 +00:00
docker run -v /path/to/models:/models ghcr.io/ggerganov/llama.cpp:full --all-in-one "/models/" 7B
2023-03-17 09:47:06 +00:00
```
2023-04-19 19:52:14 +00:00
On completion, you are ready to play!
2023-03-17 09:47:06 +00:00
```bash
2023-04-06 06:56:58 +00:00
docker run -v /path/to/models:/models ghcr.io/ggerganov/llama.cpp:full --run -m /models/7B/ggml-model-q4_0.bin -p "Building a website can be done in 10 simple steps:" -n 512
2023-03-17 09:47:06 +00:00
```
2023-04-19 19:52:14 +00:00
or with a light image:
2023-03-17 09:47:06 +00:00
```bash
2023-04-06 06:56:58 +00:00
docker run -v /path/to/models:/models ghcr.io/ggerganov/llama.cpp:light -m /models/7B/ggml-model-q4_0.bin -p "Building a website can be done in 10 simple steps:" -n 512
2023-03-17 09:47:06 +00:00
```
2023-03-14 13:30:08 +00:00
2023-03-13 07:42:26 +00:00
### Contributing
2023-03-13 17:21:51 +00:00
- Contributors can open PRs
2023-03-16 06:55:13 +00:00
- Collaborators can push to branches in the `llama.cpp` repo and merge PRs into the `master` branch
2023-03-13 07:42:26 +00:00
- Collaborators will be invited based on contributions
2023-03-16 06:55:13 +00:00
- Any help with managing issues and PRs is very appreciated!
2023-03-17 18:30:04 +00:00
- Make sure to read this: [Inference at the edge ](https://github.com/ggerganov/llama.cpp/discussions/205 )
2023-03-23 08:46:58 +00:00
- A bit of backstory for those who are interested: [Changelog podcast ](https://changelog.com/podcast/532 )
2023-03-13 07:42:26 +00:00
2023-03-14 07:43:52 +00:00
### Coding guidelines
2023-03-13 07:42:26 +00:00
- Avoid adding third-party dependencies, extra files, extra headers, etc.
- Always consider cross-compatibility with other operating systems and architectures
2023-03-14 07:43:52 +00:00
- Avoid fancy looking modern STL constructs, use basic `for` loops, avoid templates, keep it simple
2023-03-13 07:42:26 +00:00
- There are no strict rules for the code style, but try to follow the patterns in the code (indentation, spaces, etc.). Vertical alignment makes things more readable and easier to batch edit
2023-04-19 19:52:14 +00:00
- Clean-up any trailing whitespaces, use 4 spaces for indentation, brackets on the same line, `void * ptr` , `int & a`
2023-03-14 07:43:52 +00:00
- See [good first issues ](https://github.com/ggerganov/llama.cpp/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22 ) for tasks suitable for first contributions
2023-03-23 11:30:40 +00:00
2023-04-05 15:56:20 +00:00
### Docs
- [GGML tips & tricks ](https://github.com/ggerganov/llama.cpp/wiki/GGML-Tips-&-Tricks )
2023-06-05 20:32:36 +00:00
- [Performance troubleshooting ](./docs/token_generation_performance_tips.md )