Model library / llm-jp
llm-jp-4.1-33b-thinking is a 33.2 billion-parameter Japanese Llama model fine-tuned with SFT and DPO for reasoning tasks.
Parameters in total
Context length in tokens, as published
Weights at the released precision
Licence declared on the repository
Overview
The model is part of the llm-jp-4.1 series created by the Research and Development Center for Large Language Models at the National Institute of Informatics. It is a dense Transformer-based language model, post-trained using supervised fine-tuning and direct preference optimisation, and is intended for instruction-following and reasoning applications in Japanese.
In practice the model occupies roughly 33 billion parameters and runs in bfloat16 precision. It supports a context window of 65,536 tokens, allowing long-range interactions. Distribution is under the Apache-2.0 licence, facilitating commercial and research use. Deployment must accommodate the large memory footprint and ensure the provided tokenizer is used.
Specification
| Repository | llm-jp/llm-jp-4.1-33b-thinking |
| Publisher | llm-jp |
| Published | 16 September 2026 |
| Architecture | LlamaForCausalLM |
| Model type | llama |
| Parameters | 33,219,548,160 |
| Layers | 64 |
| Hidden size | 5,120 |
| Attention heads | 40, 8 key/value heads |
| Context length | 65,536 tokens |
| Vocabulary | 196,608 tokens |
| Weight format | bfloat16 |
| Licence | apache-2.0 |
Memory
Parameter count multiplied by the bytes each format uses. The key-value cache comes on top.
| Precision | Weights | Notes |
|---|---|---|
| bf16 | 61.9 GiB | Full precision as released |
| fp8 | 30.9 GiB | 8-bit, near-lossless on most models |
| int4 | 15.5 GiB | 4-bit, smallest footprint |
The cache costs 256 KiB per token at 16-bit, so the full 65,536-token context of one request needs about 16.0 GiB. Concurrency multiplies that number, not the weights.
Hardware
At the released precision, with 90% of the card given to the server and 2.5 GiB kept for the runtime. The context column is what is left for the cache on that setup.
| GPU | Cards needed | Free for cache | Context it holds |
|---|---|---|---|
| RTX 4090 24GB | 4 | 14.5 GiB | about 59,489 tokens |
| RTX 5090 32GB | 4 | 43.3 GiB | the full 65,536 tokens |
| L40S 48GB | 2 | 19.5 GiB | the full 65,536 tokens |
| A100 80GB | 1 | 7.6 GiB | about 31,226 tokens |
| H100 80GB | 1 | 7.6 GiB | about 31,226 tokens |
| RTX PRO 6000 96GB | 1 | 22.0 GiB | the full 65,536 tokens |
| H200 141GB | 1 | 62.5 GiB | the full 65,536 tokens |
Serving
A vLLM launch line for the shape above. Check the model card for a runtime the publisher recommends.
vllm serve llm-jp/llm-jp-4.1-33b-thinking \ --max-model-len 57344 \ --gpu-memory-utilization 0.90
Questions
The weights take about 62 GiB at the released precision. That fits on one A100 80GB, which leaves roughly 8 GiB for the key-value cache.
The repository declares apache-2.0. Read the licence text before commercial use: the name alone does not tell you what is allowed.
The configuration allows 65,536 tokens. Whether the whole window is usable depends on the memory left for the cache, which the hardware table works out per card.
This page is a reference, and Aiqre does not serve this model today. We deploy open-weight models on dedicated EU hardware on request, so if you want an OpenAI-compatible endpoint for it, email hello@aiqre.com with the model name and roughly what volume you expect.
Also in the library
llm-jp-4.1-32b-a3b-thinking is a 32-billion-parameter MoE Japanese language model fine-tuned with SFT and DPO.
Hy-Memory-30B-A3B is a Tencent-developed long-term-memory writer model designed to replace LLMs in Mem0, MemOS and Hy-Memory fram…
Granite Switch 4.1 30B is a modular LLM combining a 30-billion base, decision and guardian adapters, and an English speech-to-tex…
Sabi-Noema-MLA is a 27.4 B-parameter agentic model derived from Qwen3.8-27B, using multi-head latent attention to reduce attentio…
Hosting
Tell us the model and roughly what volume you expect. We reply with a price and an OpenAI-compatible endpoint, with your prompts never stored.