Model reference · open weights

AtmicEmbeddingv3

Embeddings SriRamanaAtmic Embeddings 1 build Open weights 584 dl/mo

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 bySriRamanaAtmic
TypeEmbedding models
TaskEmbeddings
Parameters (lead)560M
Context514 tokens
Based onSriRamanaAtmic/AtmicEmbeddingv2
Released2026-08-22
Popularity584 downloads / month
Weights1.1 GB (AtmicEmbeddingv3 (FP32), file size)
LicenceOpen weights

What it runs on

Memory and cards for AtmicEmbeddingv3 (FP32)

Weights 1.1 GB (file size) · overhead about 1.1 GB.

CardRunsCounted
memory
RTX 3060 12 GBfits11.6 GB
RTX 4060 Ti 16 GBfits15.4 GB
RTX 3090 24 GBfits23.4 GB
RTX 4090 24 GBfits23.4 GB
RTX 5090 32 GBfits31.0 GB
L40S 48 GBfits44.0 GB
A100 80 GBfits78.2 GB
H100 80 GBfits78.1 GB
RTX PRO 6000 Blackwell 96 GBfits93.8 GB
DGX Spark (GB10) 128 GB unifiedfits107 GB
H200 141 GBfits138 GB
B200 180 GBfits176 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

What SriRamanaAtmic says about AtmicEmbeddingv3

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)

  • 1,368 pre-mined theoretical-dialogue triplets (question/positive/negative_1-3, deduped where slots repeated — 3,176 total training rows, 1,666 unique passages). Every row gets 3 negatives; where a source doesn't already supply them, negative_1 is drawn from a 100-chunk pool of genuinely mistaken interpretations of Ramana's teaching (extracted from a scholarly critique, then rewritten to strip named-interpreter attribution), and all negative selection uses hybrid dense+BM25 scoring (Reciprocal Rank Fusion). Use query: / passage: prefixes + mean pooling + L2 normalize.
Read the full model card

Benchmarks

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):

Metricbase e5-largev2v3
Triplet accuracy0.6110.5320.884
Recall@10.2510.2330.415
Recall@50.4910.4660.651
MRR@100.3610.3480.521
NDCG@100.3990.3920.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):

Metricbase e5-largev2v3
Triplet accuracy0.7750.9260.812
Recall@10.5920.7780.571
Recall@50.8000.9570.789
MRR@100.6820.8520.675
NDCG@100.7170.8830.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.

© 2026 AxForge · EU-hosted AI infrastructure Pricing Docs Trust Privacy Terms