ED

EdgeRunner Command Nested

EdgerunnerGGUF by mradermacherUpdated 2024-10-11
Download on Hugging Face
Parameters7.6B
Context32K
Layers28
Architectureqwen2
Smallest quant1.9 GB
Quick answer

EdgeRunner Command Nested needs about 5.7 GB of memory at Q4_K_M (a 4.7 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 24 quants, from 1.9 GB (IQ1_S) to 6.3 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 1.9 GB.

EdgeRunner Command Nested – 7.6B Qwen2 model in GGUF format

EdgeRunner Command Nested is a 7.6B parameter Qwen2 model quantized into GGUF files. It supports a 32,768 token context window and is released under the apache-2.0 license. The model is available in multiple quantization levels, from IQ1_S to Q6_K.

Good at

  • Large context handling
  • Efficient inference on moderate VRAM
  • Flexible quantization options

Limits

  • No vision capabilities
  • Requires 8k context for memory estimates
  • No mixture of experts

Best for

  • Chatbot development
  • Text generation with long context
  • Low‑memory inference setups

Who it’s for. Developers building chat or text generation applications who need a large context window and flexible memory options. The model is suitable for users with access to GGUF-compatible inference engines such as llama.cpp.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
IQ1_S1.9 GB 2.9 GB
Fits Get file →
IQ1_M2.0 GB 3.0 GB
Fits Get file →
IQ2_XXS2.3 GB 3.2 GB
Fits Get file →
IQ2_XS2.5 GB 3.4 GB
Fits Get file →
IQ2_S2.6 GB 3.6 GB
Fits Get file →
IQ2_M2.8 GB 3.8 GB
Fits Get file →
Q2_K3.0 GB 4.0 GB
Fits Get file →
IQ3_XXS3.1 GB 4.1 GB
Fits Get file →
IQ3_XS3.3 GB 4.3 GB
Fits Get file →
Q3_K_S3.5 GB 4.5 GB
Fits Get file →
IQ3_S3.5 GB 4.5 GB
Fits Get file →
IQ3_M3.6 GB 4.5 GB
Fits Get file →
Q3_K_M3.8 GB 4.8 GB
Fits Get file →
Q3_K_L4.1 GB 5.1 GB
Fits Get file →
IQ4_XS4.2 GB 5.2 GB
Fits Get file →
Q4_04.4 GB 5.4 GB
Fits Get file →
Q4_04.4 GB 5.4 GB
Fits Get file →
Q4_04.4 GB 5.4 GB
Fits Get file →
Q4_04.4 GB 5.4 GB
Fits Get file →
Q4_K_S4.5 GB 5.4 GB
Fits Get file →
Q4_K_M4.7 GB 5.7 GB
Fits Get file →
Q5_K_S5.3 GB 6.3 GB
Fits Get file →
Q5_K_M5.4 GB 6.4 GB
Fits Get file →
Q6_K6.3 GB 7.2 GB
Tight Get file →

For 8‑GB VRAM, use IQ2_XS (2.47 GB file, ~3.4 GB memory) or Q3_K_S (3.49 GB file, ~4.5 GB memory). For 16‑GB VRAM, Q4_K_M (4.68 GB file, ~5.7 GB memory) or Q5_K_S (5.32 GB file, ~6.3 GB memory) provide a good balance of size and quality. Higher quants like Q6_K (6.25 GB file, ~7.2 GB memory) are suitable for systems with 24‑GB or more VRAM.

What GPU do you need for EdgeRunner Command Nested?

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 Q2_K (3.0 GB file, about 4.0 GB in use).
  • 6 GB VRAM: the best quant that fits is Q4_K_M (4.7 GB file, about 5.7 GB in use).
  • 8 GB VRAM: the best quant that fits is Q6_K (6.3 GB file, about 7.2 GB in use).

Which EdgeRunner Command Nested quant should you choose?

Q4_K_M is the usual starting point for EdgeRunner Command Nested: it balances file size and quality well. Here it is a 4.7 GB file.

If memory is tight, the smallest file is IQ1_S at 1.9 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

Architectureqwen2
Parameters7.6B
Layers28
Trained context32,768 tokens
KV cache (fp16)56 KB per token

Source

Quantized bymradermacher
Licenseapache-2.0
Downloads (HF)1,880
Last updated2024-10-11

Frequently asked questions about EdgeRunner Command Nested

How much VRAM does EdgeRunner Command Nested need?

About 5.7 GB at Q4_K_M with an 8K context window. That is the 4.7 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 EdgeRunner Command Nested on an 8 GB GPU?

Yes, with Q6_K: the 6.3 GB file needs about 7.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of EdgeRunner Command Nested GGUF?

It depends on the quant: IQ1_S is 1.9 GB, IQ1_M is 2.0 GB, IQ2_XXS is 2.3 GB, IQ2_XS is 2.5 GB, IQ2_S is 2.6 GB, IQ2_M is 2.8 GB and 18 more.

What context length does EdgeRunner Command Nested support?

The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.5 GB at 8K and 1.9 GB at 32K.

Where can I download EdgeRunner Command Nested GGUF?

The files are on Hugging Face in the mradermacher/EdgeRunner-Command-Nested-i1-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does EdgeRunner Command Nested use?

Hugging Face lists the license as apache-2.0. 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 EdgeRunner Command Nested on 8 GB VRAM?

Yes, using IQ2_XS or Q3_K_S quants will fit within 8 GB VRAM with estimated memory usage of 3.4 GB and 4.5 GB respectively.

Does the model support vision tasks?

No, the model has no vision capabilities.

What is the context length of this model?

The model supports a 32,768 token context window.

Other GGUFs of EdgeRunner-Command-Nested

Similar models

Browse all →

More from mradermacher

All by mradermacher →

More Edgerunner models

All Edgerunner →

Other small models

All small models →