[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-github-qdrant-minimize-latency":3,"mdc-y0to2d-key":47,"related-org-github-qdrant-minimize-latency":267,"related-repo-github-qdrant-minimize-latency":432},{"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-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},"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},"Performance","performance","tag",{"name":17,"slug":18,"type":15},"Architecture","architecture",{"name":20,"slug":21,"type":15},"Qdrant","qdrant",{"name":23,"slug":24,"type":15},"Database","database",{"name":26,"slug":27,"type":15},"Search","search",36978,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","2026-04-18T04:46:10.126667",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\u002Fminimize-latency","---\nname: qdrant-minimize-latency\ndescription: \"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'.\"\n---\n\n# Scaling for Query Latency\n\nLatency of a single query is determined by the slowest component in the query execution path. It is sometimes correlated with throughput, but not always — throughput and latency are opposite tuning directions.\n\nLow latency optimization is aimed at utilising maximum resource saturation for a single query, while throughput optimization is aimed at minimizing per-query resource usage to allow more parallel queries.\n\n## Performance Tuning for Lower Latency\n\n- Increase segment count to match CPU cores (`default_segment_number: 16`) [Minimizing latency](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimize\u002F?s=minimizing-latency)\n- Keep quantized vectors and HNSW in RAM (`always_ram=true`)\n- Reduce `hnsw_ef` at query time (trade recall for speed) [Search params](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimize\u002F?s=fine-tuning-search-parameters)\n- Use local NVMe, avoid network-attached storage\n\n## Memory Pressure and Latency\n\nRAM is the most critical resource for latency. If working set exceeds available RAM, OS cache eviction causes severe, sustained latency degradation.\n\n- Vertical scale RAM first. Critical if working set >80%.\n- Use quantization: scalar (4x reduction) or binary (16x reduction) [Quantization](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fquantization\u002F)\n- Move payload indexes to disk if filtering is infrequent [On-disk payload index](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Findexing\u002F?s=on-disk-payload-index)\n- Set `optimizer_cpu_budget` to limit background optimization CPUs\n- Schedule indexing: set high `indexing_threshold` during peak hours\n\n\n## Vertical Scaling for Latency\n\nMore RAM and faster CPU directly reduce latency. See [Vertical Scaling](..\u002Fscaling-data-volume\u002Fvertical-scaling\u002FSKILL.md) for node sizing guidelines.\n\n\n## What NOT to Do\n\n- Do not expect to optimize latency and throughput simultaneously on the same node\n- Do not use few large segments for latency-sensitive workloads (each segment takes longer to search)\n- Do not run at >90% RAM (cache eviction causes severe latency degradation that can last days)\n- Do not ignore optimizer status during performance debugging\n- Do not scale down RAM without load testing (cache eviction causes days-long latency incidents)\n",{"data":48,"body":49},{"name":4,"description":6},{"type":50,"children":51},"root",[52,61,67,72,79,145,151,156,214,220,233,239],{"type":53,"tag":54,"props":55,"children":57},"element","h1",{"id":56},"scaling-for-query-latency",[58],{"type":59,"value":60},"text","Scaling for Query Latency",{"type":53,"tag":62,"props":63,"children":64},"p",{},[65],{"type":59,"value":66},"Latency of a single query is determined by the slowest component in the query execution path. It is sometimes correlated with throughput, but not always — throughput and latency are opposite tuning directions.",{"type":53,"tag":62,"props":68,"children":69},{},[70],{"type":59,"value":71},"Low latency optimization is aimed at utilising maximum resource saturation for a single query, while throughput optimization is aimed at minimizing per-query resource usage to allow more parallel queries.",{"type":53,"tag":73,"props":74,"children":76},"h2",{"id":75},"performance-tuning-for-lower-latency",[77],{"type":59,"value":78},"Performance Tuning for Lower Latency",{"type":53,"tag":80,"props":81,"children":82},"ul",{},[83,107,120,140],{"type":53,"tag":84,"props":85,"children":86},"li",{},[87,89,96,98],{"type":59,"value":88},"Increase segment count to match CPU cores (",{"type":53,"tag":90,"props":91,"children":93},"code",{"className":92},[],[94],{"type":59,"value":95},"default_segment_number: 16",{"type":59,"value":97},") ",{"type":53,"tag":99,"props":100,"children":104},"a",{"href":101,"rel":102},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimize\u002F?s=minimizing-latency",[103],"nofollow",[105],{"type":59,"value":106},"Minimizing latency",{"type":53,"tag":84,"props":108,"children":109},{},[110,112,118],{"type":59,"value":111},"Keep quantized vectors and HNSW in RAM (",{"type":53,"tag":90,"props":113,"children":115},{"className":114},[],[116],{"type":59,"value":117},"always_ram=true",{"type":59,"value":119},")",{"type":53,"tag":84,"props":121,"children":122},{},[123,125,131,133],{"type":59,"value":124},"Reduce ",{"type":53,"tag":90,"props":126,"children":128},{"className":127},[],[129],{"type":59,"value":130},"hnsw_ef",{"type":59,"value":132}," at query time (trade recall for speed) ",{"type":53,"tag":99,"props":134,"children":137},{"href":135,"rel":136},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimize\u002F?s=fine-tuning-search-parameters",[103],[138],{"type":59,"value":139},"Search params",{"type":53,"tag":84,"props":141,"children":142},{},[143],{"type":59,"value":144},"Use local NVMe, avoid network-attached storage",{"type":53,"tag":73,"props":146,"children":148},{"id":147},"memory-pressure-and-latency",[149],{"type":59,"value":150},"Memory Pressure and Latency",{"type":53,"tag":62,"props":152,"children":153},{},[154],{"type":59,"value":155},"RAM is the most critical resource for latency. If working set exceeds available RAM, OS cache eviction causes severe, sustained latency degradation.",{"type":53,"tag":80,"props":157,"children":158},{},[159,164,176,188,201],{"type":53,"tag":84,"props":160,"children":161},{},[162],{"type":59,"value":163},"Vertical scale RAM first. Critical if working set >80%.",{"type":53,"tag":84,"props":165,"children":166},{},[167,169],{"type":59,"value":168},"Use quantization: scalar (4x reduction) or binary (16x reduction) ",{"type":53,"tag":99,"props":170,"children":173},{"href":171,"rel":172},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fquantization\u002F",[103],[174],{"type":59,"value":175},"Quantization",{"type":53,"tag":84,"props":177,"children":178},{},[179,181],{"type":59,"value":180},"Move payload indexes to disk if filtering is infrequent ",{"type":53,"tag":99,"props":182,"children":185},{"href":183,"rel":184},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Findexing\u002F?s=on-disk-payload-index",[103],[186],{"type":59,"value":187},"On-disk payload index",{"type":53,"tag":84,"props":189,"children":190},{},[191,193,199],{"type":59,"value":192},"Set ",{"type":53,"tag":90,"props":194,"children":196},{"className":195},[],[197],{"type":59,"value":198},"optimizer_cpu_budget",{"type":59,"value":200}," to limit background optimization CPUs",{"type":53,"tag":84,"props":202,"children":203},{},[204,206,212],{"type":59,"value":205},"Schedule indexing: set high ",{"type":53,"tag":90,"props":207,"children":209},{"className":208},[],[210],{"type":59,"value":211},"indexing_threshold",{"type":59,"value":213}," during peak hours",{"type":53,"tag":73,"props":215,"children":217},{"id":216},"vertical-scaling-for-latency",[218],{"type":59,"value":219},"Vertical Scaling for Latency",{"type":53,"tag":62,"props":221,"children":222},{},[223,225,231],{"type":59,"value":224},"More RAM and faster CPU directly reduce latency. See ",{"type":53,"tag":99,"props":226,"children":228},{"href":227},"..\u002Fscaling-data-volume\u002Fvertical-scaling\u002FSKILL.md",[229],{"type":59,"value":230},"Vertical Scaling",{"type":59,"value":232}," for node sizing guidelines.",{"type":53,"tag":73,"props":234,"children":236},{"id":235},"what-not-to-do",[237],{"type":59,"value":238},"What NOT to Do",{"type":53,"tag":80,"props":240,"children":241},{},[242,247,252,257,262],{"type":53,"tag":84,"props":243,"children":244},{},[245],{"type":59,"value":246},"Do not expect to optimize latency and throughput simultaneously on the same node",{"type":53,"tag":84,"props":248,"children":249},{},[250],{"type":59,"value":251},"Do not use few large segments for latency-sensitive workloads (each segment takes longer to search)",{"type":53,"tag":84,"props":253,"children":254},{},[255],{"type":59,"value":256},"Do not run at >90% RAM (cache eviction causes severe latency degradation that can last days)",{"type":53,"tag":84,"props":258,"children":259},{},[260],{"type":59,"value":261},"Do not ignore optimizer status during performance debugging",{"type":53,"tag":84,"props":263,"children":264},{},[265],{"type":59,"value":266},"Do not scale down RAM without load testing (cache eviction causes days-long latency incidents)",{"items":268,"total":431},[269,285,301,317,325,341,355,367,379,391,407,419],{"slug":270,"name":270,"fn":271,"description":272,"org":273,"tags":274,"stars":28,"repoUrl":29,"updatedAt":284},"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},[275,278,279,282,283],{"name":276,"slug":277,"type":15},"AI Infrastructure","ai-infrastructure",{"name":17,"slug":18,"type":15},{"name":280,"slug":281,"type":15},"Capacity Planning","capacity-planning",{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},"2026-04-18T04:46:16.349561",{"slug":286,"name":286,"fn":287,"description":288,"org":289,"tags":290,"stars":28,"repoUrl":29,"updatedAt":300},"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},[291,294,295,298,299],{"name":292,"slug":293,"type":15},"Data Engineering","data-engineering",{"name":23,"slug":24,"type":15},{"name":296,"slug":297,"type":15},"ETL","etl",{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-04-18T04:46:02.766357",{"slug":302,"name":302,"fn":303,"description":304,"org":305,"tags":306,"stars":28,"repoUrl":29,"updatedAt":316},"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},[307,310,311,314,315],{"name":308,"slug":309,"type":15},"Cost Optimization","cost-optimization",{"name":23,"slug":24,"type":15},{"name":312,"slug":313,"type":15},"Observability","observability",{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-04-18T04:46:01.525023",{"slug":4,"name":4,"fn":5,"description":6,"org":318,"tags":319,"stars":28,"repoUrl":29,"updatedAt":30},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[320,321,322,323,324],{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":26,"slug":27,"type":15},{"slug":326,"name":326,"fn":327,"description":328,"org":329,"tags":330,"stars":28,"repoUrl":29,"updatedAt":340},"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},[331,334,337,338,339],{"name":332,"slug":333,"type":15},"Debugging","debugging",{"name":335,"slug":336,"type":15},"Monitoring","monitoring",{"name":312,"slug":313,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-04-18T04:46:06.450784",{"slug":342,"name":342,"fn":343,"description":344,"org":345,"tags":346,"stars":28,"repoUrl":29,"updatedAt":354},"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},[347,348,349,350,351],{"name":276,"slug":277,"type":15},{"name":335,"slug":336,"type":15},{"name":312,"slug":313,"type":15},{"name":20,"slug":21,"type":15},{"name":352,"slug":353,"type":15},"SRE","sre","2026-04-18T04:46:05.217192",{"slug":356,"name":356,"fn":357,"description":358,"org":359,"tags":360,"stars":28,"repoUrl":29,"updatedAt":366},"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},[361,362,363,364,365],{"name":276,"slug":277,"type":15},{"name":17,"slug":18,"type":15},{"name":280,"slug":281,"type":15},{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},"2026-04-18T04:46:07.684464",{"slug":368,"name":368,"fn":369,"description":370,"org":371,"tags":372,"stars":28,"repoUrl":29,"updatedAt":378},"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},[373,374,375,376,377],{"name":276,"slug":277,"type":15},{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-04-18T04:46:08.905219",{"slug":380,"name":380,"fn":381,"description":382,"org":383,"tags":384,"stars":28,"repoUrl":29,"updatedAt":390},"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},[385,386,387,388,389],{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":26,"slug":27,"type":15},"2026-04-18T04:46:11.371326",{"slug":392,"name":392,"fn":393,"description":394,"org":395,"tags":396,"stars":28,"repoUrl":29,"updatedAt":406},"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},[397,400,403,404,405],{"name":398,"slug":399,"type":15},"Analytics","analytics",{"name":401,"slug":402,"type":15},"Data Quality","data-quality",{"name":332,"slug":333,"type":15},{"name":20,"slug":21,"type":15},{"name":26,"slug":27,"type":15},"2026-04-18T04:46:17.579894",{"slug":408,"name":408,"fn":409,"description":410,"org":411,"tags":412,"stars":28,"repoUrl":29,"updatedAt":418},"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},[413,414,415,416,417],{"name":398,"slug":399,"type":15},{"name":23,"slug":24,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":26,"slug":27,"type":15},"2026-04-18T04:46:03.987332",{"slug":420,"name":420,"fn":421,"description":422,"org":423,"tags":424,"stars":28,"repoUrl":29,"updatedAt":430},"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},[425,426,427,428,429],{"name":276,"slug":277,"type":15},{"name":398,"slug":399,"type":15},{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":26,"slug":27,"type":15},"2026-04-18T04:46:18.812306",45,{"items":433,"total":490},[434,442,450,458,466,474,482],{"slug":270,"name":270,"fn":271,"description":272,"org":435,"tags":436,"stars":28,"repoUrl":29,"updatedAt":284},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[437,438,439,440,441],{"name":276,"slug":277,"type":15},{"name":17,"slug":18,"type":15},{"name":280,"slug":281,"type":15},{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},{"slug":286,"name":286,"fn":287,"description":288,"org":443,"tags":444,"stars":28,"repoUrl":29,"updatedAt":300},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[445,446,447,448,449],{"name":292,"slug":293,"type":15},{"name":23,"slug":24,"type":15},{"name":296,"slug":297,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":302,"name":302,"fn":303,"description":304,"org":451,"tags":452,"stars":28,"repoUrl":29,"updatedAt":316},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[453,454,455,456,457],{"name":308,"slug":309,"type":15},{"name":23,"slug":24,"type":15},{"name":312,"slug":313,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":4,"name":4,"fn":5,"description":6,"org":459,"tags":460,"stars":28,"repoUrl":29,"updatedAt":30},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[461,462,463,464,465],{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":26,"slug":27,"type":15},{"slug":326,"name":326,"fn":327,"description":328,"org":467,"tags":468,"stars":28,"repoUrl":29,"updatedAt":340},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[469,470,471,472,473],{"name":332,"slug":333,"type":15},{"name":335,"slug":336,"type":15},{"name":312,"slug":313,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":342,"name":342,"fn":343,"description":344,"org":475,"tags":476,"stars":28,"repoUrl":29,"updatedAt":354},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[477,478,479,480,481],{"name":276,"slug":277,"type":15},{"name":335,"slug":336,"type":15},{"name":312,"slug":313,"type":15},{"name":20,"slug":21,"type":15},{"name":352,"slug":353,"type":15},{"slug":356,"name":356,"fn":357,"description":358,"org":483,"tags":484,"stars":28,"repoUrl":29,"updatedAt":366},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[485,486,487,488,489],{"name":276,"slug":277,"type":15},{"name":17,"slug":18,"type":15},{"name":280,"slug":281,"type":15},{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},15]