SV

Jeesup svd safety l3 swift jbbcal2 remove50

SvdGGUF by tinyopsecUpdated 2026-11-01
Download on Hugging Face
Parameters8.03B
Context8K
Layers32
Architecturellama
Smallest quant3.2 GB
Quick answer

Jeesup svd safety l3 swift jbbcal2 remove50 needs about 6.5 GB of memory at Q4_K_M (a 4.9 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 13 quants, from 3.2 GB (Q2_K) to 16.1 GB (F16).

Jeesup svd safety l3 swift jbbcal2 remove50 – a compressed Llama‑3‑8B‑Instruct checkpoint

This model is a Swift‑SVD compressed Llama‑3‑8B‑Instruct checkpoint reduced to 50.0% of dense parameters. It includes LoRA recovery and is intended for safety/utility trade‑off research. The model is not a general‑purpose chat assistant.

Good at

  • Safety research
  • Compression studies
  • LoRA recovery evaluation

Limits

  • Not a general‑purpose assistant
  • Safety‑degraded in some configurations
  • Requires evaluation before use

Best for

  • Safety trade‑off experiments
  • Compression impact analysis
  • LoRA recovery testing

Who it’s for. Researchers and developers studying the effects of SVD compression on safety and performance. The model is a research artifact and should be evaluated before deployment.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K3.2 GB 4.8 GB
Fits Get file →
Q3_K_S3.7 GB 5.2 GB
Fits Get file →
Q3_K_M4.0 GB 5.6 GB
Fits Get file →
Q3_K_L4.3 GB 5.9 GB
Fits Get file →
Q4_04.7 GB 6.2 GB
Fits Get file →
Q4_K_S4.7 GB 6.3 GB
Fits Get file →
Q4_K_M4.9 GB 6.5 GB
Fits Get file →
Q5_05.6 GB 7.2 GB
Fits Get file →
Q5_K_S5.6 GB 7.2 GB
Fits Get file →
Q5_K_M5.7 GB 7.3 GB
Tight Get file →
Q6_K6.6 GB 8.2 GB
Too big Get file →
Q8_08.5 GB 10.1 GB
Too big Get file →
F1616.1 GB 17.6 GB
Too big Get file →

For 8 GB VRAM use Q4_K_M (file size 4.92 GB, estimated 6.5 GB memory). For 16 GB VRAM use Q5_K_M (file size 5.73 GB, estimated 7.3 GB memory). For 32 GB VRAM use Q6_K (file size 6.6 GB, estimated 8.2 GB memory).

What GPU do you need for Jeesup svd safety l3 swift jbbcal2 remove50?

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: the best quant that fits is Q3_K_L (4.3 GB file, about 5.9 GB in use).
  • 8 GB VRAM: the best quant that fits is Q5_K_M (5.7 GB file, about 7.3 GB in use).
  • 12 GB VRAM: the best quant that fits is Q8_0 (8.5 GB file, about 10.1 GB in use).
  • 16 GB VRAM: the best quant that fits is Q8_0 (8.5 GB file, about 10.1 GB in use).
  • 24 GB VRAM: the best quant that fits is F16 (16.1 GB file, about 17.6 GB in use).

Which Jeesup svd safety l3 swift jbbcal2 remove50 quant should you choose?

Q4_K_M is the usual starting point for Jeesup svd safety l3 swift jbbcal2 remove50: it balances file size and quality well. Here it is a 4.9 GB file.

The Q8_0 file is 8.5 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.

If memory is tight, the smallest file is Q2_K at 3.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

Architecturellama
Parameters8.03B
Layers32
Trained context8,192 tokens
KV cache (fp16)128 KB per token

Source

Quantized bytinyopsec
FamilySvd
Licensellama3
Downloads (HF)611
Last updated2026-11-01

Frequently asked questions about Jeesup svd safety l3 swift jbbcal2 remove50

How much VRAM does Jeesup svd safety l3 swift jbbcal2 remove50 need?

About 6.5 GB at Q4_K_M with an 8K context window. That is the 4.9 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 Jeesup svd safety l3 swift jbbcal2 remove50 on an 8 GB GPU?

Yes, with Q5_K_M: the 5.7 GB file needs about 7.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of Jeesup svd safety l3 swift jbbcal2 remove50 GGUF?

It depends on the quant: Q2_K is 3.2 GB, Q3_K_S is 3.7 GB, Q3_K_M is 4.0 GB, Q3_K_L is 4.3 GB, Q4_0 is 4.7 GB, Q4_K_S is 4.7 GB and 7 more.

What context length does Jeesup svd safety l3 swift jbbcal2 remove50 support?

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

Where can I download Jeesup svd safety l3 swift jbbcal2 remove50 GGUF?

The files are on Hugging Face in the tinyopsec/Jeesup-svd-safety-l3_swift_jbbcal2_remove50-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 Jeesup svd safety l3 swift jbbcal2 remove50 use?

Hugging Face lists the license as llama3. 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?

Yes, the Q4_K_M quantization requires about 6.5 GB of VRAM at 8 k context, which fits within an 8 GB budget.

Does this model support vision?

No, the model has no vision capabilities.

What license applies to this model?

It is licensed under the Meta Llama 3 Community License, as stated in the repository.

Similar models

Browse all →

More from tinyopsec

All by tinyopsec →

More Svd models

All Svd →

Other small models

All small models →