japanese mistral 300m base needs about 1.1 GB of memory at Q4_K_M (a 0.2 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 7 quants, from 0.2 GB (Q2_K) to 0.7 GB.
Japanese Mistral 300M base – 0.355B parameters
The Japanese Mistral 300M base model is a 0.355B parameter LLaMA‑style architecture. It was trained on Wikipedia and cc100 datasets with a 4096 token context window. The model is available in multiple GGUF quantizations.
Good at
- Japanese language generation
- Fine‑tuning on small datasets
- Low‑memory inference
Limits
- No vision support
- License not specified
- Context limited to 4096 tokens
Best for
- Chatbot prototypes
- Japanese text summarization
- Script generation
Who it’s for. Developers needing a lightweight Japanese language model for local inference. Suitable for projects that require quick deployment on modest hardware.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 0.2 GB | 0.9 GB | Fits | Get file → | |
| Q3_K_M | 0.2 GB | 0.9 GB | Fits | Get file → | |
| Q4_K_M | 0.2 GB | 0.9 GB | Fits | Get file → | |
| Q5_K_M | 0.3 GB | 1.0 GB | Fits | Get file → | |
| Q6_K | 0.3 GB | 1.0 GB | Fits | Get file → | |
| Q8_0 | 0.4 GB | 1.1 GB | Fits | Get file → | |
| — | 0.7 GB | 1.4 GB | Fits | Get file → |
For 8 GB VRAM, Q4_K_M (0.23 GB) or Q5_K_M (0.27 GB) are suitable, both estimating about 1.1–1.2 GB memory at 8 k context. If memory is tighter, Q3_K_M (0.20 GB) or Q2_K (0.18 GB) can be used with similar memory usage. The unknown quant is larger and not recommended for low‑budget setups.
What GPU do you need for japanese mistral 300m base?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is the main file (0.7 GB file, about 1.6 GB in use).
Which japanese mistral 300m base quant should you choose?
Q4_K_M is the usual starting point for japanese mistral 300m base: it balances file size and quality well. Here it is a 0.2 GB file.
The Q8_0 file is 0.4 GB, about 1.6 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is Q2_K at 0.2 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about japanese mistral 300m base
How much VRAM does japanese mistral 300m base need?
About 1.1 GB at Q4_K_M with an 8K context window. That is the 0.2 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run japanese mistral 300m base on an 8 GB GPU?
Yes, with the smaller files: the 0.7 GB file needs about 1.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of japanese mistral 300m base GGUF?
It depends on the quant: Q2_K is 0.2 GB, Q3_K_M is 0.2 GB, Q4_K_M is 0.2 GB, Q5_K_M is 0.3 GB, Q6_K is 0.3 GB, Q8_0 is 0.4 GB and 1 more.
What context length does japanese mistral 300m base support?
The GGUF header lists a trained context length of 4,096 tokens (4K). The KV cache grows with the context you use: about 0.4 GB at 8K and 0.2 GB at 4K.
Where can I download japanese mistral 300m base GGUF?
The files are on Hugging Face in the afrideva/japanese-mistral-300m-base-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run this model on 8 GB VRAM?
Yes, Q4_K_M or Q5_K_M quantizations fit within 8 GB VRAM, using roughly 1.1–1.2 GB memory at 8 k context.
Does this model support vision tasks?
No, the model has no vision capabilities.
What is the maximum context length?
The model supports up to 4096 tokens of context.