qdrant-scaling
Guides Qdrant scaling decisions. Use when someone asks 'how many nodes do I need', 'data doesn't fit on one node', 'need more throughput', 'cluster …
它会碰到什么
这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。
技能内容
Qdrant Scaling
First determine what you're scaling for:
- data volume
- query throughput (QPS)
- query latency
- query volume
After determining the scaling goal, we can choose scaling strategy based on tradeoffs and assumptions.
Each pulls toward different strategies. Scaling for throughput and latency are opposite tuning directions.
Scaling Data Volume
This becomes relevant when volume of the dataset exceeds the capacity of a single node.
Read more about scaling for data volume in [Scaling Data Volume](scaling-data-volume/SKILL.md)
Scaling for Query Throughput
If your system needs to handle more parallel queries than a single node can handle,
then you need to scale for query throughput.
Read more about scaling for query throughput in [Scaling for Query Throughput](scaling-qps/SKILL.md)
Scaling for Query Latency
Latency of a single query is determined by the slowest component in the query execution path.
It is in sometimes correlated with throughput, but not always. It might require different strategies for scaling.
Read more about scaling for query latency in [Scaling for Query Latency](minimize-latency/SKILL.md)
Scaling for Query Volume
By query volume we understand the amount of results that a single query returns.
If the query volume is too high, it can cause performance issues and increase latency.
Tuning for query volume is opposite might require special strategies.
Read more about scaling for query volume in [Scaling for Query Volume](scaling-query-volume/SKILL.md)
想直接用这个技能？
本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。