README.md 11.2 KB
Newer Older
chenxl's avatar
chenxl committed
1
2
3
<div align="center">
  <!-- <h1>KTransformers</h1> -->
  <p align="center">
chenxl's avatar
chenxl committed
4
5

<picture>
UnicornChan's avatar
UnicornChan committed
6
    <img alt="KTransformers" src="https://github.com/user-attachments/assets/d5a2492f-a415-4456-af99-4ab102f13f8b" width=50%>
Mingxing Zhang's avatar
Mingxing Zhang committed
7

chenxl's avatar
chenxl committed
8
</picture>
UnicornChan's avatar
UnicornChan committed
9

chenxl's avatar
chenxl committed
10
</p>
chenxl's avatar
chenxl committed
11
  <h3>A Flexible Framework for Experiencing Cutting-edge LLM Inference Optimizations</h3>
Azure's avatar
Azure committed
12
  <strong><a href="#show-cases">🌟 Show Cases</a> | <a href="#quick-start">🚀 Quick Start</a> | <a href="#tutorial">📃 Tutorial</a> | <a href="https://github.com/kvcache-ai/ktransformers/discussions">💬  Discussion </a>|<a href="#FAQ"> 🙋 FAQ</a> </strong>
chenxl's avatar
chenxl committed
13
14
15
16
17
18
19
20
21
22
23
</div>

<h2 id="intro">🎉 Introduction</h2>
KTransformers, pronounced as Quick Transformers, is designed to enhance your 🤗 <a href="https://github.com/huggingface/transformers">Transformers</a> experience with advanced kernel optimizations and placement/parallelism strategies.
<br/><br/>
KTransformers is a flexible, Python-centric framework designed with extensibility at its core. 
By implementing and injecting an optimized module with a single line of code, users gain access to a Transformers-compatible
interface, RESTful APIs compliant with OpenAI and Ollama, and even a simplified ChatGPT-like web UI. 
<br/><br/>
Our vision for KTransformers is to serve as a flexible platform for experimenting with innovative LLM inference optimizations. Please let us know if you need any other features.

chenxl's avatar
chenxl committed
24
<h2 id="Updates">🔥 Updates</h2>
Azure's avatar
Azure committed
25

djw's avatar
djw committed
26
* **Apr 9, 2025**: Experimental support for LLaMA 4 models ([Tutorial](./en/llama4.md)).
dongjw's avatar
dongjw committed
27
* **Apr 2, 2025**: Support Multi-concurrency. ([Tutorial](./doc/en/balance-serve.md)).
dongjw's avatar
dongjw committed
28
29
30

https://github.com/user-attachments/assets/faa3bda2-928b-45a7-b44f-21e12ec84b8a

31
* **Mar 15, 2025**: Support ROCm on AMD GPU ([Tutorial](./doc/en/ROCm.md)).
Atream's avatar
Atream committed
32
* **Mar 5, 2025**: Support unsloth 1.58/2.51 bits weights and [IQ1_S/FP8 hybrid](./doc/en/fp8_kernel.md) weights. Support 139K [Longer Context](./doc/en/DeepseekR1_V3_tutorial.md#v022--v023-longer-context--fp8-kernel) for DeepSeek-V3 and R1 in 24GB VRAM.
33
* **Feb 25, 2025**: Support [FP8 GPU kernel](./doc/en/fp8_kernel.md) for DeepSeek-V3 and R1; [Longer Context](./doc/en/DeepseekR1_V3_tutorial.md#v022-longer-context).
Azure's avatar
Azure committed
34
* **Feb 15, 2025**: Longer Context (from 4K to 8K for 24GB VRAM) & Slightly Faster Speed (+15%, up to 16 Tokens/s), update [docs](./doc/en/DeepseekR1_V3_tutorial.md) and [online books](https://kvcache-ai.github.io/ktransformers/).
Azure's avatar
Azure committed
35
* **Feb 10, 2025**: Support Deepseek-R1 and V3 on single (24GB VRAM)/multi gpu and 382G DRAM, up to 3~28x speedup. For detailed show case and reproduction tutorial, see [here](./doc/en/DeepseekR1_V3_tutorial.md).
TangJingqi's avatar
TangJingqi committed
36
* **Aug 28, 2024**: Decrease DeepseekV2's required VRAM from 21G to 11G.
37
38
* **Aug 15, 2024**: Update detailed [tutorial](doc/en/injection_tutorial.md) for injection and multi-GPU.
* **Aug 14, 2024**: Support llamfile as linear backend.
Azure's avatar
Azure committed
39
40
* **Aug 12, 2024**: Support multiple GPU; Support new model: mixtral 8\*7B  and 8\*22B; Support q2k, q3k, q5k dequant on gpu.
* **Aug 9, 2024**: Support windows native.
41

Azure's avatar
Azure committed
42
<!-- * **Aug 28, 2024**: Support 1M context under the InternLM2.5-7B-Chat-1M model, utilizing 24GB of VRAM and 150GB of DRAM. The detailed tutorial is [here](./doc/en/long_context_tutorial.md). -->
43

liam's avatar
liam committed
44
<h2 id="show-cases">🌟 Show Cases</h2>
UnicornChan's avatar
UnicornChan committed
45

liam's avatar
liam committed
46
47
48
<div>
<h3>GPT-4/o1-level Local VSCode Copilot on a Desktop with only 24GB VRAM</h3>
</div>
chenxl's avatar
chenxl committed
49

liam's avatar
liam committed
50
https://github.com/user-attachments/assets/ebd70bfa-b2c1-4abb-ae3b-296ed38aa285
chenxl's avatar
chenxl committed
51
52
53

</p>

Azure's avatar
Azure committed
54
- **[NEW!!!] Local 671B DeepSeek-Coder-V3/R1:** Running its Q4_K_M version using only 14GB VRAM and 382GB DRAM([Tutorial](./doc/en/DeepseekR1_V3_tutorial.md)).
liam's avatar
liam committed
55

56
57
58
59
60
61
62
63
64
  - Prefill Speed (tokens/s):
    - KTransformers: 54.21 (32 cores) → 74.362 (dual-socket, 2×32 cores) → 255.26 (optimized AMX-based MoE kernel, V0.3 only) → 286.55 (selectively using 6 experts, V0.3 only)
    - Compared to 10.31 tokens/s in llama.cpp with 2×32 cores, achieving up to **27.79× speedup**.
  - Decode Speed (tokens/s):
    - KTransformers: 8.73 (32 cores) → 11.26 (dual-socket, 2×32 cores) → 13.69 (selectively using 6 experts, V0.3 only)
    - Compared to 4.51 tokens/s in llama.cpp with 2×32 cores, achieving up to **3.03× speedup**.
  - Upcoming Open Source Release:
    - AMX optimizations and selective expert activation will be open-sourced in V0.3.
    - Currently available only in preview binary distribution, which can be downloaded [here](./doc/en/DeepseekR1_V3_tutorial.md).
liam's avatar
liam committed
65
66
- **Local 236B DeepSeek-Coder-V2:** Running its Q4_K_M version using only 21GB VRAM and 136GB DRAM, attainable on a local desktop machine, which scores even better than GPT4-0613 in [BigCodeBench](https://huggingface.co/blog/leaderboard-bigcodebench).

chenxl's avatar
chenxl committed
67
68
<p align="center">
  <picture>
liam's avatar
liam committed
69
    <img alt="DeepSeek-Coder-V2 Score" src="https://github.com/user-attachments/assets/d052924e-8631-44de-aad2-97c54b965693" width=100%>
chenxl's avatar
chenxl committed
70
71
72
  </picture>
</p>

liam's avatar
liam committed
73
74
- **Faster Speed:** Achieving 126 tokens/s for 2K prompt prefill and 13.6 tokens/s for generation through MoE offloading and injecting advanced kernels from [Llamafile](https://github.com/Mozilla-Ocho/llamafile/tree/main) and [Marlin](https://github.com/IST-DASLab/marlin).
- **VSCode Integration:** Wrapped into an OpenAI and Ollama compatible API for seamless integration as a backend for [Tabby](https://github.com/TabbyML/tabby) and various other frontends.
chenxl's avatar
chenxl committed
75

liam's avatar
liam committed
76
<p align="center">
chenxl's avatar
chenxl committed
77

liam's avatar
liam committed
78
https://github.com/user-attachments/assets/4c6a8a38-05aa-497d-8eb1-3a5b3918429c
UnicornChan's avatar
UnicornChan committed
79

chenxl's avatar
chenxl committed
80
81
</p>

Azure's avatar
Azure committed
82
<!-- <h3>1M Context Local Inference on a Desktop with Only 24GB VRAM</h3>
liam's avatar
liam committed
83
84
85
86
87
<p align="center">

https://github.com/user-attachments/assets/a865e5e4-bca3-401e-94b8-af3c080e6c12

* **1M Context InternLM 2.5 7B**: Operates at full bf16 precision, utilizing 24GB VRAM and 150GB DRAM, which is feasible on a local desktop setup. It achieves a 92.88% success rate on the 1M "Needle In a Haystack" test and 100% on the 128K NIAH test.
chenxl's avatar
chenxl committed
88
89
90

<p align="center">
  <picture>
liam's avatar
liam committed
91
    <img alt="Single Needle Retrieval 128K" src="./doc/assets/needle_128K.png" width=100%>
chenxl's avatar
chenxl committed
92
93
94
95
  </picture>
</p>

<p align="center">
liam's avatar
liam committed
96
97
98
99
100
101
102
103
  <picture>
    <img alt="Single Needle Retrieval 1000K" src="./doc/assets/needle_1M.png" width=100%>
  </picture>
</p>

* **Enhanced Speed**: Reaches 16.91 tokens/s for generation with a 1M context using sparse attention, powered by llamafile kernels. This method is over 10 times faster than full attention approach of llama.cpp.

* **Flexible Sparse Attention Framework**: Offers a flexible block sparse attention framework for CPU offloaded decoding. Compatible with SnapKV, Quest, and InfLLm. Further information is available [here](./doc/en/long_context_introduction.md).
Azure's avatar
Azure committed
104
 -->
UnicornChan's avatar
UnicornChan committed
105

chenxl's avatar
chenxl committed
106
107
108
109
<strong>More advanced features will coming soon, so stay tuned!</strong>

<h2 id="quick-start">🚀 Quick Start</h2>

Azure's avatar
Azure committed
110
Getting started with KTransformers is simple! Follow the steps below to set up and start using it.
chenxl's avatar
chenxl committed
111

Azure's avatar
Azure committed
112
### 📥 Installation
chenxl's avatar
chenxl committed
113

_'s avatar
_ committed
114
To install KTransformers, follow the official [Installation Guide](https://kvcache-ai.github.io/ktransformers/en/install.html).
chenxl's avatar
chenxl committed
115
116
117

<h2 id="tutorial">📃 Brief Injection Tutorial</h2>
At the heart of KTransformers is a user-friendly, template-based injection framework. 
chenxl's avatar
chenxl committed
118
This allows researchers to easily replace original torch modules with optimized variants. It also simplifies the process of combining multiple optimizations, allowing the exploration of their synergistic effects.
chenxl's avatar
chenxl committed
119
120
121
122

</br>
<p align="center">
  <picture>
UnicornChan's avatar
UnicornChan committed
123
    <img alt="Inject-Struction" src="https://github.com/user-attachments/assets/6b4c1e54-9f6d-45c5-a3fc-8fa45e7d257e" width=65%>
chenxl's avatar
chenxl committed
124
125
126
127
128
129
130
131
132
133
134
  </picture>
</p>

Given that vLLM already serves as a great framework for large-scale deployment optimizations, KTransformers is particularly focused on local deployments that are constrained by limited resources. We pay special attention to heterogeneous computing opportunities, such as GPU/CPU offloading of quantized models. For example, we support the efficient <a herf="https://github.com/Mozilla-Ocho/llamafile/tree/main">Llamafile</a> and <a herf="https://github.com/IST-DASLab/marlin">Marlin</a> kernels for CPU and GPU, respectively. More details can be found <a herf="doc/en/operators/llamafile.md">here</a>.

<h3>Example Usage</h3>
To utilize the provided kernels, users only need to create a YAML-based injection template and add the call to `optimize_and_load_gguf` before using the Transformers model.

```python
with torch.device("meta"):
    model = AutoModelForCausalLM.from_config(config, trust_remote_code=True)
Azure's avatar
Azure committed
135
optimize_and_load_gguf(model, optimize_config_path, gguf_path, config)
chenxl's avatar
chenxl committed
136
137
138
139
140
141
142
143
...
generated = prefill_and_generate(model, tokenizer, input_tensor.cuda(), max_new_tokens=1000)
```

In this example, the AutoModel is first initialized on the meta device to avoid occupying any memory resources. Then, `optimize_and_load_gguf` iterates through all sub-modules of the model, matches rules specified in your YAML rule file, and replaces them with advanced modules as specified.

After injection, the original `generate` interface is available, but we also provide a compatible `prefill_and_generate` method, which enables further optimizations like CUDAGraph to improve generation speed.

144
145
146
147
<h3>How to custom your model</h3>

A detailed tutorial of the injection and multi-GPU using DeepSeek-V2 as an example is given [here](doc/en/injection_tutorial.md).

chenxl's avatar
chenxl committed
148
149
150
151
152
153
154
Below is an example of a YAML template for replacing all original Linear modules with Marlin, an advanced 4-bit quantization kernel.

```yaml
- match:
    name: "^model\\.layers\\..*$"  # regular expression 
    class: torch.nn.Linear  # only match modules matching name and class simultaneously
  replace:
155
    class: ktransformers.operators.linear.KTransformerLinear  # optimized Kernel on quantized data types
chenxl's avatar
chenxl committed
156
157
158
    device: "cpu"   # which devices to load this module when initializing
    kwargs:
      generate_device: "cuda"
159
      generate_linear_type: "QuantizedLinearMarlin"
chenxl's avatar
chenxl committed
160
161
162
163
164
165
```

Each rule in the YAML file has two parts: `match` and `replace`. The `match` part specifies which module should be replaced, and the `replace` part specifies the module to be injected into the model along with the initialization keywords.

You can find example rule templates for optimizing DeepSeek-V2 and Qwen2-57B-A14, two SOTA MoE models, in the [ktransformers/optimize/optimize_rules](ktransformers/optimize/optimize_rules) directory. These templates are used to power the `local_chat.py` demo.

166
If you are interested in our design principles and the implementation of the injection framework, please refer to the [design document](doc/en/deepseek-v2-injection.md).
chenxl's avatar
chenxl committed
167
168
169

<h2 id="ack">Acknowledgment and Contributors</h2>

170
The development of KTransformers is based on the flexible and versatile framework provided by Transformers. We also benefit from advanced kernels such as GGUF/GGML, Llamafile, Marlin, sglang and flashinfer. We are planning to contribute back to the community by upstreaming our modifications.
chenxl's avatar
chenxl committed
171

172
KTransformers is actively maintained and developed by contributors from the <a href="https://madsys.cs.tsinghua.edu.cn/">MADSys group</a> at Tsinghua University and members from <a href="http://approaching.ai/">Approaching.AI</a>. We welcome new contributors to join us in making KTransformers faster and easier to use.
Atream's avatar
Atream committed
173
174
175

<h2 id="ack">Discussion</h2>

ZiWei Yuan's avatar
ZiWei Yuan committed
176
If you have any questions, feel free to open an issue. Alternatively, you can join our WeChat group for further discussion. QR Code: [WeChat Group](WeChatGroup.png)
Azure's avatar
Azure committed
177
178
179

<h2 id="FAQ">🙋 FAQ</h2>

feeeei's avatar
feeeei committed
180
Some common questions are answered in the [FAQ](doc/en/FAQ.md).