VI

T VisStar v0.1

VisstarGGUF by mradermacherUpdated 2024-12-16
Download on Hugging Face
Parameters7.3B
Context32K
Layers32
Architecturellama
Smallest quant2.7 GB
Quick answer

T VisStar v0.1 needs about 6.0 GB of memory at Q4_K_M (a 4.4 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 15 quants, from 2.7 GB (Q2_K) to 14.6 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.3 GB.

T VisStar v0.1 – a 7.3B llama‑based model

T VisStar v0.1 is a 7.3B parameter llama model fine‑tuned from T‑VisStar‑7B‑v0.1. It supports a 32768 token context window and is released under the apache‑2.0 license. The model is available in multiple GGUF quantizations.

Good at

  • Large context handling
  • Flexible quantization options
  • Open‑source licensing

Limits

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

Best for

  • Chat assistants with long context
  • Fine‑tuning on custom datasets
  • Running on local hardware with limited VRAM

Who it’s for. Developers and researchers who need a large llama model with a long context window and open‑source licensing. The model is suitable for local deployment using llama.cpp or transformers.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K2.7 GB 4.3 GB
Fits Get file →
IQ3_XS3.1 GB 4.6 GB
Fits Get file →
Q3_K_S3.2 GB 4.8 GB
Fits Get file →
IQ3_S3.2 GB 4.8 GB
Fits Get file →
IQ3_M3.3 GB 4.9 GB
Fits Get file →
Q3_K_M3.6 GB 5.1 GB
Fits Get file →
Q3_K_L3.9 GB 5.4 GB
Fits Get file →
IQ4_XS4.0 GB 5.6 GB
Fits Get file →
Q4_K_S4.2 GB 5.8 GB
Fits Get file →
Q4_K_M4.4 GB 6.0 GB
Fits Get file →
Q5_K_S5.0 GB 6.6 GB
Fits Get file →
Q5_K_M5.2 GB 6.7 GB
Fits Get file →
Q6_K6.0 GB 7.6 GB
Tight Get file →
Q8_07.8 GB 9.3 GB
Too big Get file →
F1614.6 GB 16.2 GB
Too big Get file →

For 8 GB VRAM, use Q4_K_M (file size 4.4 GB, estimated memory 6 GB) or Q5_K_S (file size 5.04 GB, estimated memory 6.6 GB). For 12 GB VRAM, Q5_K_M (file size 5.17 GB, estimated memory 6.7 GB) or Q6_K (file size 5.99 GB, estimated memory 7.6 GB) are suitable. Higher‑precision quants like Q8_0 or F16 require more than 16 GB VRAM.

What GPU do you need for T VisStar 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: the best quant that fits is Q4_K_M (4.4 GB file, about 6.0 GB in use).
  • 8 GB VRAM: the best quant that fits is Q6_K (6.0 GB file, about 7.6 GB in use).
  • 12 GB VRAM: the best quant that fits is Q8_0 (7.8 GB file, about 9.3 GB in use).
  • 16 GB VRAM: the best quant that fits is Q8_0 (7.8 GB file, about 9.3 GB in use).
  • 24 GB VRAM: the best quant that fits is F16 (14.6 GB file, about 16.2 GB in use).

Which T VisStar v0.1 quant should you choose?

Q4_K_M is the usual starting point for T VisStar v0.1: it balances file size and quality well. Here it is a 4.4 GB file.

The Q8_0 file is 7.8 GB, about 1.8 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 2.7 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
Parameters7.3B
Layers32
Trained context32,768 tokens
KV cache (fp16)128 KB per token

Source

Quantized bymradermacher
FamilyVisstar
Licenseapache-2.0
Downloads (HF)1,196
Last updated2024-12-16

Frequently asked questions about T VisStar v0.1

How much VRAM does T VisStar v0.1 need?

About 6.0 GB at Q4_K_M with an 8K context window. That is the 4.4 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 T VisStar v0.1 on an 8 GB GPU?

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

What is the file size of T VisStar v0.1 GGUF?

It depends on the quant: Q2_K is 2.7 GB, IQ3_XS is 3.1 GB, Q3_K_S is 3.2 GB, IQ3_S is 3.2 GB, IQ3_M is 3.3 GB, Q3_K_M is 3.6 GB and 9 more.

What context length does T VisStar v0.1 support?

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

Where can I download T VisStar v0.1 GGUF?

The files are on Hugging Face in the mradermacher/T-VisStar-v0.1-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 T VisStar v0.1 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 T VisStar v0.1 on 8 GB VRAM?

Yes, using Q4_K_M or Q5_K_S quants will fit within 8 GB VRAM with estimated memory usage around 6 GB.

Does T VisStar v0.1 support vision tasks?

No, the model does not include vision capabilities.

What license applies to T VisStar v0.1?

The model is released under the apache‑2.0 license.

Other GGUFs of T-VisStar-7B-v0.1

Similar models

Browse all →

More from mradermacher

All by mradermacher →

More Visstar models

All Visstar →

Other small models

All small models →