輸入會不會超限?
一起計算文字、圖片、影片與音訊,避免超過共享的 8,192 Token 上限。
為 RAG 與多模態搜尋開發者準備:一分鐘計算輸入上限、向量儲存與合適維度。
不用翻閱多份文件或先寫測試程式,輸入一次工作量就能得到實用起點。
一起計算文字、圖片、影片與音訊,避免超過共享的 8,192 Token 上限。
估算向量、元資料、索引開銷、副本與每月費用。
比較 128–768 維並複製相符的 Python 設定。
文字、圖片、影片影格與音訊共用 8,192 Token 上限。
估算向量、元資料、索引開銷與副本。
先比較官方品質資料與儲存節省,再用自己的資料測試。
所有假設都公開,可依照工作負載調整。
Text tokens + images × visual tokens + sampled video frames × visual tokens + audio seconds × 25.
Total ≤ 8,192 tokens
Vector values and metadata are calculated first, then multiplied by index overhead and replica count.
(vectors + metadata) × (1 + overhead) × replicas
The model estimate uses selected encoder parameters × two bytes for BF16 weights. Runtime memory is additional.
parameters × 2 bytes
程式碼會隨選擇的維度與模態更新。
Start with 256d for storage-sensitive text retrieval, and 512d or 768d when code or multimodal recall matters more. Treat 128d as a text-first shortlist candidate, not a universal default. Benchmark on representative queries before re-indexing production data.
Slicing a normalized 768d vector changes its length. Re-normalizing keeps cosine similarity meaningful. Google specifically recommends using truncate_dim together with normalize_embeddings=True.
No. All calculations run in your browser. The tool does not ask for files, prompts, credentials or an API key.
No. It estimates raw BF16 weights only. Real VRAM or RAM usage also includes the framework, activations, temporary tensors, caches, media processing and operating-system overhead.
No. It is a planning estimate for vectors, metadata, index overhead and replicas. A provider may also charge for compute, operations, backups, network transfer and minimum capacity.
Yes. EmbeddingGemma 2 maps these modalities into one shared vector space, but all media and text inside one input share the same 8,192-token budget.