You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can refer to the general [*Prepare and Quantize*](README.md#prepare-and-quantize) guide for model prepration.
56
+
You can refer to the general [llama-quantize tool](/tools/quantize/README.md)for steps to convert a model in Hugging Face safetensor format to GGUF with quantization.
52
57
53
-
Currently we support `Q4_0` quantization and have optimize for it. To achieve best performance on Adreno GPU, add `--pure` to `llama-quantize`. For example,
58
+
Currently we support `Q4_0` quantization and have optimized for it. To achieve best performance on Adreno GPU, add `--pure` to `llama-quantize` (i.e., make all weights in `Q4_0`). For example,
Since `Q6_K` is also supported, `Q4_0` quantization without `--pure` will also work. However, the performance will be worse compared to pure `Q4_0` quantization.
60
65
66
+
### `MXFP4` MoE Models
67
+
68
+
OpenAI gpt-oss models are MoE models in `MXFP4`. The quantized model will be in `MXFP4_MOE`, a mixture of `MXFP4` and `Q8_0`.
69
+
For this quantization, there is no need to specify `--pure`.
70
+
For gpt-oss-20b model, you can directly [download](https://huggingface.co/ggml-org/gpt-oss-20b-GGUF) the quantized GGUF file in `MXFP4_MOE` from Hugging Face.
71
+
72
+
Although it is possible to quantize gpt-oss-20b model in pure `Q4_0` (all weights in `Q4_0`), it is not recommended since `MXFP4` has been optimized for MoE while `Q4_0` is not. In addition, accuracy should degrade with such pure `Q4_0` quantization.
73
+
Hence, using the default `MXFP4_MOE` quantization (see the link above) is recommended for this model.
74
+
75
+
> Note that the `Q4_0` model found [here](https://huggingface.co/unsloth/gpt-oss-20b-GGUF/blob/main/gpt-oss-20b-Q4_0.gguf) is a mixture of `Q4_0`, `Q8_0` and `MXFP4` and gives better performance than `MXFP4_MOE` quantization.
76
+
61
77
## CMake Options
62
78
63
79
The OpenCL backend has the following CMake options that control the behavior of the backend.
@@ -146,10 +162,13 @@ A Snapdragon X Elite device with Windows 11 Arm64 is used. Make sure the followi
146
162
* Ninja
147
163
* Visual Studio 2022
148
164
* Powershell 7
165
+
* Python
149
166
150
167
Visual Studio provides necessary headers and libraries although it is not directly used for building.
151
168
Alternatively, Visual Studio Build Tools can be installed instead of the full Visual Studio.
152
169
170
+
> Note that building using Visual Studio's cl compiler is not supported. Clang must be used. Clang depends on libraries provided by Visual Studio to work. Therefore, Visual Studio must be installed. Alternatively, Visual Studio Build Tools can be installed instead of the full Visual Studio.
171
+
153
172
Powershell 7 is used for the following commands.
154
173
If an older version of Powershell is used, these commands may not work as they are.
155
174
@@ -201,9 +220,12 @@ ninja
201
220
202
221
## Known Issues
203
222
204
-
- Currently OpenCL backend does not work on Adreno 6xx GPUs.
223
+
- Flash attention does not always improve performance.
224
+
- Currently OpenCL backend works on A6xx GPUs with recent drivers and compilers (usually found in IoT platforms).
225
+
However, it does not work on A6xx GPUs found in phones with old drivers and compilers.
0 commit comments