LA

Landmark_Detection

LandmarkGGUF by mradermacherUpdated 2025-07-31
Download on Hugging Face
Parameters1.78B
Context32K
Layers28
Architectureqwen2vl
Smallest quant0.8 GB
Quick answer

Landmark_Detection needs about 1.9 GB of memory at Q4_K_M (a 1.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 12 quants, from 0.8 GB (Q2_K) to 3.6 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.9 GB.

Landmark_Detection is a 1.78B-parameter Landmark model in GGUF format, quantized by mradermacher. Its trained context length is 32K tokens. The repository has 12 quant files, from 0.8 GB (Q2_K) to 3.6 GB (F16).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K0.8 GB 1.5 GB
Fits Get file →
Q3_K_S0.9 GB 1.6 GB
Fits Get file →
Q3_K_M0.9 GB 1.7 GB
Fits Get file →
Q3_K_L1.0 GB 1.7 GB
Fits Get file →
IQ4_XS1.0 GB 1.8 GB
Fits Get file →
Q4_K_S1.1 GB 1.8 GB
Fits Get file →
Q4_K_M1.1 GB 1.9 GB
Fits Get file →
Q5_K_S1.3 GB 2.0 GB
Fits Get file →
Q5_K_M1.3 GB 2.0 GB
Fits Get file →
Q6_K1.5 GB 2.2 GB
Fits Get file →
Q8_01.9 GB 2.6 GB
Fits Get file →
F163.6 GB 4.3 GB
Fits Get file →

What GPU do you need for Landmark_Detection?

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 Q8_0 (1.9 GB file, about 2.6 GB in use).
  • 6 GB VRAM: the best quant that fits is F16 (3.6 GB file, about 4.3 GB in use).

Which Landmark_Detection quant should you choose?

Q4_K_M is the usual starting point for Landmark_Detection: it balances file size and quality well. Here it is a 1.1 GB file.

The Q8_0 file is 1.9 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 0.8 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

Architectureqwen2vl
Parameters1.78B
Layers28
Trained context32,768 tokens
KV cache (fp16)28 KB per token

Source

Quantized bymradermacher
FamilyLandmark
Downloads (HF)64
Last updated2025-07-31

Frequently asked questions about Landmark_Detection

How much VRAM does Landmark_Detection need?

About 1.9 GB at Q4_K_M with an 8K context window. That is the 1.1 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 Landmark_Detection on an 8 GB GPU?

Yes, with F16: the 3.6 GB file needs about 4.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of Landmark_Detection GGUF?

It depends on the quant: Q2_K is 0.8 GB, Q3_K_S is 0.9 GB, Q3_K_M is 0.9 GB, Q3_K_L is 1.0 GB, IQ4_XS is 1.0 GB, Q4_K_S is 1.1 GB and 6 more.

What context length does Landmark_Detection 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.2 GB at 8K and 0.9 GB at 32K.

Where can I download Landmark_Detection GGUF?

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

Similar models

Browse all →

More from mradermacher

All by mradermacher →

More Landmark models

All Landmark →

Other tiny models

All tiny models →