Model reference · open weights
AtmicEmbeddingv3 is an open-weight embedding model from SriRamanaAtmic. AtmicEmbeddingv3 (FP32) weighs 1.1 GB; the smallest configuration that runs it is RTX 3060 12 GB.
What it is
| Released by | SriRamanaAtmic |
|---|---|
| Type | Embedding models |
| Task | Embeddings |
| Parameters (lead) | 560M |
| Context | 514 tokens |
| Based on | SriRamanaAtmic/AtmicEmbeddingv2 |
| Released | 2026-08-22 |
| Popularity | 584 downloads / month |
| Weights | 1.1 GB (AtmicEmbeddingv3 (FP32), file size) |
| Licence | Open weights |
What it runs on
Weights 1.1 GB (file size) · overhead about 1.1 GB.
| Card | Runs | Counted memory |
|---|---|---|
| RTX 3060 12 GB | fits | 11.6 GB |
| RTX 4060 Ti 16 GB | fits | 15.4 GB |
| RTX 3090 24 GB | fits | 23.4 GB |
| RTX 4090 24 GB | fits | 23.4 GB |
| RTX 5090 32 GB | fits | 31.0 GB |
| L40S 48 GB | fits | 44.0 GB |
| A100 80 GB | fits | 78.2 GB |
| H100 80 GB | fits | 78.1 GB |
| RTX PRO 6000 Blackwell 96 GB | fits | 93.8 GB |
| DGX Spark (GB10) 128 GB unified | fits | 107 GB |
| H200 141 GB | fits | 138 GB |
| B200 180 GB | fits | 176 GB |
Estimates, not measurements: the weights are the build's file size. No cache grows with use; a batch of inputs needs working memory of its own. Counted memory is 92 % of what CUDA reports for the card.
From the model card
Contrastive continue-training of AtmicEmbeddingv2 on a much larger combined corpus: 452 expert Q&A pairs + 1,356 Claude-generated paraphrase/scenario questions (same answers)
query: / passage: prefixes + mean pooling + L2 normalize.Three-way comparison — base intfloat/multilingual-e5-large (zero domain fine-tuning) vs.
v2 vs. v3 — on two test sets.
Own held-out test data (275 rows, 581-passage corpus):
| Metric | base e5-large | v2 | v3 |
|---|---|---|---|
| Triplet accuracy | 0.611 | 0.532 | 0.884 |
| Recall@1 | 0.251 | 0.233 | 0.415 |
| Recall@5 | 0.491 | 0.466 | 0.651 |
| MRR@10 | 0.361 | 0.348 | 0.521 |
| NDCG@10 | 0.399 | 0.392 | 0.566 |
v3 beats both base and v2 by a wide margin here — the larger, more diverse training set (theoretical dialogue data plus paraphrase/scenario questions) generalizes well beyond either the un-fine-tuned base model or v2's narrower specialization.
Full 161_pass dataset (644 triplets — v2's OWN original training data, used as a retention / catastrophic-forgetting check):
| Metric | base e5-large | v2 | v3 |
|---|---|---|---|
| Triplet accuracy | 0.775 | 0.926 | 0.812 |
| Recall@1 | 0.592 | 0.778 | 0.571 |
| Recall@5 | 0.800 | 0.957 | 0.789 |
| MRR@10 | 0.682 | 0.852 | 0.675 |
| NDCG@10 | 0.717 | 0.883 | 0.717 |
Honest tradeoff, stated plainly: v3's retention on 161_pass is the weakest of any AtmicEmbedding release — it has round-tripped to roughly base-model performance on this specific corpus (R@1 0.571 vs base's 0.592), losing most of the specialization v1→v2 training added there. This is a real cost of training on ~1.75x more data (3,176 vs the prior round's 1,808 rows) at the same epoch/learning-rate/freeze-layer budget, which pulls the model further from v2's weights. Notably, v2 itself underperforms base on the newer, more diverse own-test-data set (0.532 vs 0.611 accuracy) — v2 appears overfit to 161_pass's narrower style, and v3 trades that narrow strength for broader generalization. If 161_pass-specific retrieval quality matters for your use case, evaluate v3 there directly before switching from v2.
Quoted from the model card on Hugging Face — the full card is behind the Hugging Face link above.