Totvs Protheus ADVPL V0.1 needs about 7.4 GB of memory at Q4_K_M (a 5.8 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 2 quants, from 5.8 GB (Q4_K_M) to 9.8 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 4.4 GB.
Totvs Protheus ADVPL V0.1 – 9.2B Qwen3.5 model for local Protheus AI
Totvs Protheus ADVPL V0.1 is a 9.2B Qwen3.5 model trained on 262144 context tokens. It runs 100% locally, providing reasoning, tools, and vision capabilities for Protheus development.
Good at
- Reasoning on Protheus rules
- Tool usage for API and UI creation
- Vision for log and error analysis
Limits
- No internet required, no external data sent
- No vision support in local deployment
- License is other, no token cost
Best for
- Writing ADVPL code
- Debugging Protheus logs
- Creating REST APIs and PO UI
Who it’s for. Developers and consultants working with TOTVS Protheus who need a local AI assistant that understands business rules, database schema, and can diagnose errors without sending code to the cloud.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 5.8 GB | 7.4 GB | Tight | Get file → | |
| Q8_0 | 9.8 GB | 11.4 GB | Too big | Get file → |
For 8GB VRAM, use Q4_K_M (5.78GB file, ~7.4GB memory at 8k context). For larger memory budgets, Q8_0 (9.79GB file, ~11.4GB memory at 8k context) offers higher precision.
What GPU do you need for Totvs Protheus ADVPL V0.1?
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: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: the best quant that fits is Q4_K_M (5.8 GB file, about 7.4 GB in use).
- 12 GB VRAM: the best quant that fits is Q8_0 (9.8 GB file, about 11.4 GB in use).
Which Totvs Protheus ADVPL V0.1 quant should you choose?
Q4_K_M is the usual starting point for Totvs Protheus ADVPL V0.1: it balances file size and quality well. Here it is a 5.8 GB file.
The Q8_0 file is 9.8 GB, about 1.7 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.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about Totvs Protheus ADVPL V0.1
How much VRAM does Totvs Protheus ADVPL V0.1 need?
About 7.4 GB at Q4_K_M with an 8K context window. That is the 5.8 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 Totvs Protheus ADVPL V0.1 on an 8 GB GPU?
Yes, with Q4_K_M: the 5.8 GB file needs about 7.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Totvs Protheus ADVPL V0.1 GGUF?
It depends on the quant: Q4_K_M is 5.8 GB, Q8_0 is 9.8 GB.
What context length does Totvs Protheus ADVPL V0.1 support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.4 GB at 32K.
Where can I download Totvs Protheus ADVPL V0.1 GGUF?
The files are on Hugging Face in the dyulianocecilio/Totvs-Protheus-ADVPL-V0.1 repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Totvs Protheus ADVPL V0.1 use?
Hugging Face lists the license as other. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8 GB VRAM?
Q4_K_M requires about 7.4GB memory at 8k context, so 8GB VRAM should be sufficient.
Does it support vision?
The model has vision ability, but local deployment does not expose vision features.
Is there a token cost?
No token cost; the model runs locally and does not send data to external services.