输入会不会超限?
把文字、图片、视频和音频放在一起计算,避免超过共享的 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.