[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-github-qdrant-scaling-data-volume":3,"mdc--qowtb7-key":47,"related-repo-github-qdrant-scaling-data-volume":171,"related-org-github-qdrant-scaling-data-volume":272},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":28,"repoUrl":29,"updatedAt":30,"license":31,"forks":32,"topics":33,"repo":42,"sourceUrl":45,"mdContent":46},"qdrant-scaling-data-volume","scale Qdrant data volume","Guides Qdrant data volume scaling decisions. Use when someone asks 'data doesn't fit on one node', 'too much data', 'need more storage', 'vertical or horizontal scaling', 'tenant scaling', 'time window rotation', or 'data growth exceeds capacity'.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"github","GitHub","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fgithub.png",[12,16,19,22,25],{"name":13,"slug":14,"type":15},"Architecture","architecture","tag",{"name":17,"slug":18,"type":15},"Qdrant","qdrant",{"name":20,"slug":21,"type":15},"Database","database",{"name":23,"slug":24,"type":15},"Capacity Planning","capacity-planning",{"name":26,"slug":27,"type":15},"AI Infrastructure","ai-infrastructure",36978,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","2026-04-18T04:46:07.684464",null,4632,[34,35,36,37,38,39,40,41],"agent-skills","agents","ai","awesome","custom-agents","github-copilot","hacktoberfest","prompt-engineering",{"repoUrl":29,"stars":28,"forks":32,"topics":43,"description":44},[34,35,36,37,38,39,40,41],"Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002FHEAD\u002Fskills\u002Fqdrant-scaling\u002Fscaling-data-volume","---\nname: qdrant-scaling-data-volume\ndescription: \"Guides Qdrant data volume scaling decisions. Use when someone asks 'data doesn't fit on one node', 'too much data', 'need more storage', 'vertical or horizontal scaling', 'tenant scaling', 'time window rotation', or 'data growth exceeds capacity'.\"\nallowed-tools:\n  - Read\n  - Grep\n  - Glob\n---\n\n# Scaling Data Volume\n\nThis document covers data volume scaling scenarios,\nwhere the total size of the dataset exceeds the capacity of a single node.\n\n## Tenant Scaling\n\nIf the use case is multi-tenant, meaning that each user only has access to a subset of the data,\nand we never need to query across all the data, then we can use multi-tenancy patterns to scale.\n\nThe recommended way is to use multi-tenant workloads with payload partitioning, per-tenant indexes, and tiered multitenancy.\n\nLearn more [Tenant Scaling](tenant-scaling\u002FSKILL.md)\n\n## Sliding Time Window\n\nSome use-cases are based on a sliding time window, where only the most recent data is relevant.\nFor example an index for social media posts, where only the last 6 months of data require fast search.\n\nLearn more [Sliding Time Window](sliding-time-window\u002FSKILL.md)\n\n## Global Search\n\nMost general use-cases require global search across all data.\nIn these situations, we might need to fall back to vertical scaling,\nand then horizontal scaling when we reach the limits of vertical scaling.\n\n\n### Vertical Scaling\n\nWhen data doesn't fit in a single node, the first approach is to scale the node itself — more RAM, better disk, quantization, mmap.\nExhaust vertical options before going horizontal, as horizontal scaling adds permanent operational complexity.\n\nLearn more [Vertical Scaling](vertical-scaling\u002FSKILL.md)\n\n### Horizontal Scaling\n\nWhen a single node can't hold the data even with quantization and mmap, distribute data across multiple nodes via sharding.\n\nLearn more [Horizontal Scaling](horizontal-scaling\u002FSKILL.md)\n",{"data":48,"body":53},{"name":4,"description":6,"allowed-tools":49},[50,51,52],"Read","Grep","Glob",{"type":54,"children":55},"root",[56,65,71,78,83,88,99,105,110,119,125,130,137,142,151,157,162],{"type":57,"tag":58,"props":59,"children":61},"element","h1",{"id":60},"scaling-data-volume",[62],{"type":63,"value":64},"text","Scaling Data Volume",{"type":57,"tag":66,"props":67,"children":68},"p",{},[69],{"type":63,"value":70},"This document covers data volume scaling scenarios,\nwhere the total size of the dataset exceeds the capacity of a single node.",{"type":57,"tag":72,"props":73,"children":75},"h2",{"id":74},"tenant-scaling",[76],{"type":63,"value":77},"Tenant Scaling",{"type":57,"tag":66,"props":79,"children":80},{},[81],{"type":63,"value":82},"If the use case is multi-tenant, meaning that each user only has access to a subset of the data,\nand we never need to query across all the data, then we can use multi-tenancy patterns to scale.",{"type":57,"tag":66,"props":84,"children":85},{},[86],{"type":63,"value":87},"The recommended way is to use multi-tenant workloads with payload partitioning, per-tenant indexes, and tiered multitenancy.",{"type":57,"tag":66,"props":89,"children":90},{},[91,93],{"type":63,"value":92},"Learn more ",{"type":57,"tag":94,"props":95,"children":97},"a",{"href":96},"tenant-scaling\u002FSKILL.md",[98],{"type":63,"value":77},{"type":57,"tag":72,"props":100,"children":102},{"id":101},"sliding-time-window",[103],{"type":63,"value":104},"Sliding Time Window",{"type":57,"tag":66,"props":106,"children":107},{},[108],{"type":63,"value":109},"Some use-cases are based on a sliding time window, where only the most recent data is relevant.\nFor example an index for social media posts, where only the last 6 months of data require fast search.",{"type":57,"tag":66,"props":111,"children":112},{},[113,114],{"type":63,"value":92},{"type":57,"tag":94,"props":115,"children":117},{"href":116},"sliding-time-window\u002FSKILL.md",[118],{"type":63,"value":104},{"type":57,"tag":72,"props":120,"children":122},{"id":121},"global-search",[123],{"type":63,"value":124},"Global Search",{"type":57,"tag":66,"props":126,"children":127},{},[128],{"type":63,"value":129},"Most general use-cases require global search across all data.\nIn these situations, we might need to fall back to vertical scaling,\nand then horizontal scaling when we reach the limits of vertical scaling.",{"type":57,"tag":131,"props":132,"children":134},"h3",{"id":133},"vertical-scaling",[135],{"type":63,"value":136},"Vertical Scaling",{"type":57,"tag":66,"props":138,"children":139},{},[140],{"type":63,"value":141},"When data doesn't fit in a single node, the first approach is to scale the node itself — more RAM, better disk, quantization, mmap.\nExhaust vertical options before going horizontal, as horizontal scaling adds permanent operational complexity.",{"type":57,"tag":66,"props":143,"children":144},{},[145,146],{"type":63,"value":92},{"type":57,"tag":94,"props":147,"children":149},{"href":148},"vertical-scaling\u002FSKILL.md",[150],{"type":63,"value":136},{"type":57,"tag":131,"props":152,"children":154},{"id":153},"horizontal-scaling",[155],{"type":63,"value":156},"Horizontal Scaling",{"type":57,"tag":66,"props":158,"children":159},{},[160],{"type":63,"value":161},"When a single node can't hold the data even with quantization and mmap, distribute data across multiple nodes via sharding.",{"type":57,"tag":66,"props":163,"children":164},{},[165,166],{"type":63,"value":92},{"type":57,"tag":94,"props":167,"children":169},{"href":168},"horizontal-scaling\u002FSKILL.md",[170],{"type":63,"value":156},{"items":172,"total":271},[173,185,203,219,233,249,263],{"slug":174,"name":174,"fn":175,"description":176,"org":177,"tags":178,"stars":28,"repoUrl":29,"updatedAt":184},"qdrant-horizontal-scaling","guide Qdrant horizontal scaling decisions","Diagnoses and guides Qdrant horizontal scaling decisions. Use when someone asks 'vertical or horizontal?', 'how many nodes?', 'how many shards?', 'how to add nodes', 'resharding', 'data doesn't fit', or 'need more capacity'. Also use when data growth outpaces current deployment.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[179,180,181,182,183],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:16.349561",{"slug":186,"name":186,"fn":187,"description":188,"org":189,"tags":190,"stars":28,"repoUrl":29,"updatedAt":202},"qdrant-indexing-performance-optimization","optimize Qdrant indexing performance","Diagnoses and fixes slow Qdrant indexing and data ingestion. Use when someone reports 'uploads are slow', 'indexing takes forever', 'optimizer is stuck', 'HNSW build time too long', or 'data uploaded but search is bad'. Also use when optimizer status shows errors, segments won't merge, or indexing threshold questions arise.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[191,194,195,198,201],{"name":192,"slug":193,"type":15},"Data Engineering","data-engineering",{"name":20,"slug":21,"type":15},{"name":196,"slug":197,"type":15},"ETL","etl",{"name":199,"slug":200,"type":15},"Performance","performance",{"name":17,"slug":18,"type":15},"2026-04-18T04:46:02.766357",{"slug":204,"name":204,"fn":205,"description":206,"org":207,"tags":208,"stars":28,"repoUrl":29,"updatedAt":218},"qdrant-memory-usage-optimization","optimize Qdrant memory usage","Diagnoses and reduces Qdrant memory usage. Use when someone reports 'memory too high', 'RAM keeps growing', 'node crashed', 'out of memory', 'memory leak', or asks 'why is memory usage so high?', 'how to reduce RAM?'. Also use when memory doesn't match calculations, quantization didn't help, or nodes crash during recovery.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[209,212,213,216,217],{"name":210,"slug":211,"type":15},"Cost Optimization","cost-optimization",{"name":20,"slug":21,"type":15},{"name":214,"slug":215,"type":15},"Observability","observability",{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:01.525023",{"slug":220,"name":220,"fn":221,"description":222,"org":223,"tags":224,"stars":28,"repoUrl":29,"updatedAt":232},"qdrant-minimize-latency","minimize Qdrant query latency","Guides Qdrant query latency optimization. Use when someone asks 'search is slow', 'how to reduce latency', 'p99 is too high', 'tail latency', 'single query too slow', 'how to make search faster', or 'latency spikes'.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[225,226,227,228,229],{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},{"name":230,"slug":231,"type":15},"Search","search","2026-04-18T04:46:10.126667",{"slug":234,"name":234,"fn":235,"description":236,"org":237,"tags":238,"stars":28,"repoUrl":29,"updatedAt":248},"qdrant-monitoring-debugging","debug Qdrant production issues with metrics","Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[239,242,245,246,247],{"name":240,"slug":241,"type":15},"Debugging","debugging",{"name":243,"slug":244,"type":15},"Monitoring","monitoring",{"name":214,"slug":215,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:06.450784",{"slug":250,"name":250,"fn":251,"description":252,"org":253,"tags":254,"stars":28,"repoUrl":29,"updatedAt":262},"qdrant-monitoring-setup","set up Qdrant monitoring and alerting","Guides Qdrant monitoring setup including Prometheus scraping, health probes, Hybrid Cloud metrics, alerting, and log centralization. Use when someone asks 'how to set up monitoring', 'Prometheus config', 'Grafana dashboard', 'health check endpoints', 'how to scrape Hybrid Cloud', 'what alerts to set', 'how to centralize logs', or 'audit logging'.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[255,256,257,258,259],{"name":26,"slug":27,"type":15},{"name":243,"slug":244,"type":15},{"name":214,"slug":215,"type":15},{"name":17,"slug":18,"type":15},{"name":260,"slug":261,"type":15},"SRE","sre","2026-04-18T04:46:05.217192",{"slug":4,"name":4,"fn":5,"description":6,"org":264,"tags":265,"stars":28,"repoUrl":29,"updatedAt":30},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[266,267,268,269,270],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},{"name":17,"slug":18,"type":15},15,{"items":273,"total":394},[274,282,290,298,306,314,322,330,342,354,370,382],{"slug":174,"name":174,"fn":175,"description":176,"org":275,"tags":276,"stars":28,"repoUrl":29,"updatedAt":184},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[277,278,279,280,281],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},{"name":17,"slug":18,"type":15},{"slug":186,"name":186,"fn":187,"description":188,"org":283,"tags":284,"stars":28,"repoUrl":29,"updatedAt":202},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[285,286,287,288,289],{"name":192,"slug":193,"type":15},{"name":20,"slug":21,"type":15},{"name":196,"slug":197,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},{"slug":204,"name":204,"fn":205,"description":206,"org":291,"tags":292,"stars":28,"repoUrl":29,"updatedAt":218},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[293,294,295,296,297],{"name":210,"slug":211,"type":15},{"name":20,"slug":21,"type":15},{"name":214,"slug":215,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},{"slug":220,"name":220,"fn":221,"description":222,"org":299,"tags":300,"stars":28,"repoUrl":29,"updatedAt":232},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[301,302,303,304,305],{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},{"name":230,"slug":231,"type":15},{"slug":234,"name":234,"fn":235,"description":236,"org":307,"tags":308,"stars":28,"repoUrl":29,"updatedAt":248},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[309,310,311,312,313],{"name":240,"slug":241,"type":15},{"name":243,"slug":244,"type":15},{"name":214,"slug":215,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},{"slug":250,"name":250,"fn":251,"description":252,"org":315,"tags":316,"stars":28,"repoUrl":29,"updatedAt":262},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[317,318,319,320,321],{"name":26,"slug":27,"type":15},{"name":243,"slug":244,"type":15},{"name":214,"slug":215,"type":15},{"name":17,"slug":18,"type":15},{"name":260,"slug":261,"type":15},{"slug":4,"name":4,"fn":5,"description":6,"org":323,"tags":324,"stars":28,"repoUrl":29,"updatedAt":30},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[325,326,327,328,329],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},{"name":17,"slug":18,"type":15},{"slug":331,"name":331,"fn":332,"description":333,"org":334,"tags":335,"stars":28,"repoUrl":29,"updatedAt":341},"qdrant-scaling-qps","scale Qdrant query throughput","Guides Qdrant query throughput (QPS) scaling. Use when someone asks 'how to increase QPS', 'need more throughput', 'queries per second too low', 'batch search', 'read replicas', or 'how to handle more concurrent queries'.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[336,337,338,339,340],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:08.905219",{"slug":343,"name":343,"fn":344,"description":345,"org":346,"tags":347,"stars":28,"repoUrl":29,"updatedAt":353},"qdrant-scaling-query-volume","scale Qdrant query volume and pagination","Guides Qdrant query volume scaling. Use when someone asks 'query returns too many results', 'scroll performance', 'large limit values', 'paginating search results', 'fetching many vectors', or 'high cardinality results'.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[348,349,350,351,352],{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},{"name":230,"slug":231,"type":15},"2026-04-18T04:46:11.371326",{"slug":355,"name":355,"fn":356,"description":357,"org":358,"tags":359,"stars":28,"repoUrl":29,"updatedAt":369},"qdrant-search-quality-diagnosis","diagnose Qdrant search quality issues","Diagnoses Qdrant search quality issues. Use when someone reports 'results are bad', 'wrong results', 'not relevant results', 'missing matches', 'recall is low', 'approximate search worse than exact', 'which embedding model', or 'quality dropped after quantization'. Also use when search quality degrades without obvious changes.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[360,363,366,367,368],{"name":361,"slug":362,"type":15},"Analytics","analytics",{"name":364,"slug":365,"type":15},"Data Quality","data-quality",{"name":240,"slug":241,"type":15},{"name":17,"slug":18,"type":15},{"name":230,"slug":231,"type":15},"2026-04-18T04:46:17.579894",{"slug":371,"name":371,"fn":372,"description":373,"org":374,"tags":375,"stars":28,"repoUrl":29,"updatedAt":381},"qdrant-search-speed-optimization","optimize Qdrant search speed","Diagnoses and fixes slow Qdrant search. Use when someone reports 'search is slow', 'high latency', 'queries take too long', 'low QPS', 'throughput too low', 'filtered search is slow', or 'search was fast but now it's slow'. Also use when search performance degrades after config changes or data growth.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[376,377,378,379,380],{"name":361,"slug":362,"type":15},{"name":20,"slug":21,"type":15},{"name":199,"slug":200,"type":15},{"name":17,"slug":18,"type":15},{"name":230,"slug":231,"type":15},"2026-04-18T04:46:03.987332",{"slug":383,"name":383,"fn":384,"description":385,"org":386,"tags":387,"stars":28,"repoUrl":29,"updatedAt":393},"qdrant-search-strategies","select optimal Qdrant search strategies","Guides Qdrant search strategy selection. Use when someone asks 'should I use hybrid search?', 'BM25 or sparse vectors?', 'how to rerank?', 'results are not relevant', 'I don't get needed results from my dataset but they're there', 'retrieval quality is not good enough', 'results too similar', 'need diversity', 'MMR', 'relevance feedback', 'recommendation API', 'discovery API', 'ColBERT reranking', or 'missing keyword matches'",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[388,389,390,391,392],{"name":26,"slug":27,"type":15},{"name":361,"slug":362,"type":15},{"name":13,"slug":14,"type":15},{"name":17,"slug":18,"type":15},{"name":230,"slug":231,"type":15},"2026-04-18T04:46:18.812306",45]