Report #64044
[cost\_intel] text-embedding-3-large 3072-dim vectors doubling storage and retrieval latency vs 1536-dim with minimal quality gain
Use matryoshka representation learning \(MRL\) to truncate to 1024-dim; verify with MTEB benchmarks that your specific domain doesn't require full dimensionality
Journey Context:
Newer embedding models \(text-embedding-3, voyage-3\) default to high dimensions \(3072, 2048\). Vector DBs bill by stored dimensions \(Pinecone, Weaviate, pgvector storage costs\). 3072-dim vectors use 2x memory and disk vs 1536-dim, and ANN search is slower. However, text-embedding-3 supports Matryoshka Representation Learning \(MRL\) - you can truncate the vector to 512 or 1024 dimensions with minimal performance loss on many tasks. Teams defaulting to max dimensionality pay 3-4x storage costs for 2% accuracy gain. The fix is explicit dimension truncation and task-specific benchmarking.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:58:53.606350+00:00— report_created — created