qdrant scaling
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 is slow', 'too many tenants', 'vertical or horizontal', 'how to shard', or 'need to add capacity'.
Introduction source: author · github · b6483db44fb602654bca6a097185fcaddb305f97 Reference
Author's original introduction
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 is slow', 'too many tenants', 'vertical or horizontal', 'how to shard', or 'need to add capacity'.
SkillPi interpretation
- Tasks
- qdrant scaling
- Audience
- Use the scenarios stated in the author's introduction.
- Inputs and outputs
- See the complete author document; outputs have not been runtime verified by SkillPi.
- Software, accounts and paid services
- Check required software, accounts, costs and permissions in the full document; confirm and authorize actual file access and external services in your host. Domains referenced in the documents (not a runtime allowlist): cloud.qdrant.io, github.com, qdrant.tech, search.qdrant.tech
- Limits and differences
- Functionality, version status and outcome statements in the introduction are author claims. Only pinned source and static attachment evidence were checked; runtime behavior, external services and compatibility are not guaranteed.
- Testing
- Not tested
Permissions and checks before use
Automatically summarized from this main document. Matches may be examples or defensive advice; they are not actual permission declarations. Attachments, external dependencies and runtime behavior are not covered.
These common operations were not identified in the main document. This does not mean no permissions or risks exist.
Security rating and access scope
caution · Static evidence review; not a runtime safety guarantee.
Check required software, accounts, costs and permissions in the full document; confirm and authorize actual file access and external services in your host. Domains referenced in the documents (not a runtime allowlist): cloud.qdrant.io, github.com, qdrant.tech, search.qdrant.tech
Before use, confirm and authorize actual file access, external services and network destinations in your host. This review grants no runtime permissions.
Original SKILL.md
--- name: qdrant-scaling description: "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 is slow', 'too many tenants', 'vertical or horizontal', 'how to shard', or 'need to add capacity'." allowed-tools: - Read - Grep - Glob --- # 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)
Copyright and license notice
MIT License Copyright GitHub, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
User discussion