[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE241FGDEF85P6YY4T52KF":3,"skill-same:01M6AE241FGDEF85P6YY4T52KF":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6AE241FGDEF85P6YY4T52KF","qdrant-minimize-latency",null,"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'.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fqdrant-scaling\u002Fminimize-latency\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"Qdrant","qdrant minimize latency","latency","when","search","single","reduce","high","tail","make","guides","how to","latency optimization","query","use","how","Optimization","2026-11-10 10:12:30",false,"---\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","# 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",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fqdrant-scaling\u002Fminimize-latency",5340,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 13:41:32",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add github\u002Fawesome-copilot --skill qdrant-minimize-latency",{"tool":57,"command":58},"bunx","bunx skills add github\u002Fawesome-copilot --skill qdrant-minimize-latency",{"tool":60,"command":61},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill qdrant-minimize-latency","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fqdrant-scaling\u002Fminimize-latency\u002FSKILL.md",true,[65,71],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",102,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002Fagents\u002Fopenai.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"SKILL-MECHANICS.md",2629,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL-MECHANICS.md",[76,109,137,167,200,217],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":90,"publishedAt":36},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[82,87],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":88,"categoryName":89,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000023","Skill与智能体开发",[91,92,93,94,95,22,96,97,98,99,100,101,102,103,104,105,33,106,107,108],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","users","functions","with",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":36},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[115],{"categoryNo":88,"categoryName":89,"taxonomyType":85,"taxonomyTypeDesc":86},[117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":149,"publishedAt":36},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[150,151,152,153,154,155,123,95,156,157,158,159,160,161,162,33,163,164,165,166],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":178,"publishedAt":36},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[174,177],{"categoryNo":175,"categoryName":176,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},[179,23,180,181,182,183,184,185,186,187,188,189,190,191,192,22,193,194,195,196,197,123,198,199],"winmd api search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":213,"publishedAt":36},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[208,209,212],{"categoryNo":175,"categoryName":176,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":210,"categoryName":211,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":88,"categoryName":89,"taxonomyType":85,"taxonomyTypeDesc":86},[214,120,187,215,216],"resemble detect","https","identity",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":228,"publishedAt":36},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[224,227],{"categoryNo":225,"categoryName":226,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":88,"categoryName":89,"taxonomyType":85,"taxonomyTypeDesc":86},[229,230,231,232,151,96,9,119,233,234,215,235,236,237,238,239,240,241,242,243,244,245,104,246,247,248,249],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]