Milvus 聊了向量数据库成本容易算漏的三个坑，还拿自动驾驶 10 亿行数据举例，用对方案能省十几倍钱。
Milvus 团队指出，用 demo 估算生产环境向量数据库成本常忽略三大隐性因素：数据更新（增删改、重索引）带来的计算开销、离线分析/评估任务与在线服务共用基础设施导致的工作负载错配、以及同一 AI 数据在向量搜索、湖仓、训练等系统间的重复存储。以某自动驾驶场景为例，1B 行数据集合的向量搜索每月仅需运行几小时，专用集群预估 $7,000/月，Serverless 约 $10,800/月，而 Zilliz Cloud On-Demand Search 成本不到 $500/月。建议将稳定在线流量匹配专用容量、突发在线需求用 Serverless、低频分析用按需计费。
Using a demo to estimate the real production cost of a vector database is where cost planning goes w...
Using a demo to estimate the real production cost of a vector database is where cost planning goes wrong for many teams. The demo phase can give you a reasonable answer on two things: • Storage: embeddings, raw content, metadata, scalar fields, and index files. • Online serving: the compute needed for the current query volume and latency target. But a demo usually cannot answer three other cost questions: • Updates: how often data is added, deleted, re-embedded, re-indexed, or checked for recall regressions. • Workload mismatch: whether offline analysis, evaluation, or batch jobs are running on always-on infrastructure. • Duplication: how many copies of the same AI data end up across vector search, lakehouse, training, evaluation, and governance systems. Different data scales and usage frequencies require different resource models. For example, one autonomous driving workload needed vector search over a 1B-row collection for analysis. 𝗔 𝗱𝗲𝗱𝗶𝗰𝗮𝘁𝗲𝗱 𝗰𝗹𝘂𝘀𝘁𝗲𝗿 was estimated at about $7,000 per month. 𝗦𝗲𝗿𝘃𝗲𝗿𝗹𝗲𝘀𝘀 was about $10,800 per month. But the workload only ran for a few hours each month. With 𝗭𝗶𝗹𝗹𝗶𝘇 𝗖𝗹𝗼𝘂𝗱 𝗢𝗻-𝗗𝗲𝗺𝗮𝗻𝗱 𝗦𝗲𝗮𝗿𝗰𝗵, the cost came in under $500 per month. In enterprise environments, however, these workload patterns usually coexist. A single system may have steady online traffic, offline batch processing, evaluation jobs, and sudden demand spikes. The goal is not to choose one resource model for everything. It is to accurately identify each workload and match it to the right instance type. Use dedicated capacity for steady, latency-sensitive traffic; serverless for unpredictable or spiky online demand; and on-demand compute for low-frequency analysis, evaluation, and batch jobs. 💬 0 🔄 0 ❤️ 0 👀 27 ⚡