ME

maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed

MedicalGGUF by PrunaAIUpdated 2026-03-25
Download on Hugging Face
Parameters163M
Context1K
Layers12
Architecturegpt2
Smallest quant0.1 GB
Quick answer

maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed needs about 0.9 GB of memory at Q4_K_M (a 0.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 14 quants, from 0.1 GB (Q2_K) to 0.2 GB (Q8_0).

Medical QA model fine‑tuned from GPT‑2, 0.163B parameters

This model is a GPT‑2 variant fine‑tuned on medical data. It supports up to 1024 context tokens. The model is available in multiple GGUF quantizations.

Good at

  • Medical question answering
  • Fine‑tuned GPT‑2 architecture
  • Compact GGUF files

Limits

  • No vision support
  • License not specified
  • Context limited to 1024 tokens

Best for

  • Clinical FAQ bots
  • Medical knowledge retrieval
  • Healthcare research assistants

Who it’s for. Developers building medical chatbots or knowledge bases. Researchers needing a lightweight medical QA model.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K0.1 GB 0.6 GB
Fits Get file →
Q3_K_S0.1 GB 0.6 GB
Fits Get file →
Q3_K_M0.1 GB 0.6 GB
Fits Get file →
Q3_K_L0.1 GB 0.6 GB
Fits Get file →
Q4_00.1 GB 0.6 GB
Fits Get file →
Q4_K_S0.1 GB 0.6 GB
Fits Get file →
Q4_K_M0.1 GB 0.7 GB
Fits Get file →
Q4_10.1 GB 0.7 GB
Fits Get file →
Q5_00.1 GB 0.7 GB
Fits Get file →
Q5_K_S0.1 GB 0.7 GB
Fits Get file →
Q5_K_M0.1 GB 0.7 GB
Fits Get file →
Q5_10.1 GB 0.7 GB
Fits Get file →
Q6_K0.1 GB 0.7 GB
Fits Get file →
Q8_00.2 GB 0.7 GB
Fits Get file →

For 8 GB VRAM, Q2_K (0.08 GB file, 0.9 GB memory) is suitable. Q3_K_S, Q3_K_M, Q3_K_L, Q4_0, Q4_K_S, Q4_K_M, Q5_K_M, Q6_K all fit within 8 GB VRAM. For 1 GB VRAM, Q8_0 (0.18 GB file, 1 GB memory) is the largest option. Memory estimates are approximate.

What GPU do you need for maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed?

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 (0.2 GB file, about 1.0 GB in use).

Which maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed quant should you choose?

Q4_K_M is the usual starting point for maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed: it balances file size and quality well. Here it is a 0.1 GB file.

The Q8_0 file is 0.2 GB, about 1.6 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.1 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

Architecturegpt2
Parameters163M
Layers12
Trained context1,024 tokens
KV cache (fp16)36 KB per token

Frequently asked questions about maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed

How much VRAM does maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed need?

About 0.9 GB at Q4_K_M with an 8K context window. That is the 0.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 maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed on an 8 GB GPU?

Yes, with Q8_0: the 0.2 GB file needs about 1.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed GGUF?

It depends on the quant: Q2_K is 0.1 GB, Q3_K_S is 0.1 GB, Q3_K_M is 0.1 GB, Q3_K_L is 0.1 GB, Q4_0 is 0.1 GB, Q4_K_S is 0.1 GB and 8 more.

What context length does maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed support?

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

Where can I download maheshhuggingface Medical Data Question Answers finetuned gpt2 GGUF smashed GGUF?

The files are on Hugging Face in the PrunaAI/maheshhuggingface-Medical-Data-Question-Answers-finetuned-gpt2-GGUF-smashed repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

Can I run this model on 8 GB VRAM?

Yes, the Q2_K to Q6_K quantizations all require less than 8 GB VRAM.

Does the model support image inputs?

No, the model has no vision capabilities.

What is the maximum context length?

The model is trained with 1024 context tokens.

Other GGUFs of Medical-Data-Question-Answers-finetuned-gpt2

Similar models

Browse all →

More from PrunaAI

All by PrunaAI →

More Medical models

All Medical →

Other tiny models

All tiny models →