[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VP0WAZKT30VYMXS0GS718":3,"skill-same:01M77VP0WAZKT30VYMXS0GS718":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77VP0WAZKT30VYMXS0GS718","scaling-qps",null,"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'.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fqdrant-scaling\u002Fscaling-qps\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"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'.\"\n---\n# Scaling for Query Throughput (QPS)\n\nThroughput scaling means handling more parallel queries per second. \nThis is different from latency - throughput and latency are opposite tuning directions and cannot be optimized simultaneously on the same node.\n\nHigh throughput favors fewer, larger segments so each query touches less overhead.\n\n\n## Performance Tuning for Higher RPS\n\n- Use fewer, larger segments (`default_segment_number: 2`) [Maximizing throughput](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimize\u002F?s=maximizing-throughput)\n- Enable quantization with `always_ram=true` to reduce disk IO [Quantization](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fquantization\u002F)\n- Use batch search API to amortize overhead [Batch search](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fsearch\u002Fsearch\u002F?s=batch-search-api)\n\n## Minimize impact of Update Workloads\n\n- Configure update throughput control (v1.17+) to prevent unoptimized searches degrading reads [Low latency search](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fsearch\u002Flow-latency-search\u002F)\n- Set `optimizer_cpu_budget` to limit indexing CPUs (e.g. `2` on an 8-CPU node reserves 6 for queries)\n- Configure delayed read fan-out (v1.17+) for tail latency [Delayed fan-outs](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fsearch\u002Flow-latency-search\u002F?s=use-delayed-fan-outs)\n\n\n\n## Horizontal Scaling for Throughput\n\nIf a single node is saturated on CPU after applying the tuning above, scale horizontally with read replicas.\n\n- Shard replicas serve queries from replicated shards, distributing read load across nodes\n- Each replica adds independent query capacity without re-sharding\n- Use `replication_factor: 2+` and route reads to replicas [Distributed deployment](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fdistributed_deployment\u002F?s=replication)\n\nSee also [Horizontal Scaling](..\u002Fscaling-data-volume\u002Fhorizontal-scaling\u002FSKILL.md) for general horizontal scaling guidance.\n\n\n## Disk I\u002FO Bottlenecks\n\nIf it is not possible to keep all vectors in RAM, disk I\u002FO can become the bottleneck for throughput. \nIn this case:\n\n- Upgrade to provisioned IOPS or local NVMe first. See impact of disk performance to vector search in [Disk performance article](https:\u002F\u002Fqdrant.tech\u002Farticles\u002Fmemory-consumption\u002F)\n- Use `io_uring` on Linux (kernel 5.11+) [io_uring article](https:\u002F\u002Fqdrant.tech\u002Farticles\u002Fio_uring\u002F)\n- In case of quantized vectors, prefer global rescoring over per-segment rescoring to reduce disk reads. Example in the [tutorial](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Ftutorials-operations\u002Flarge-scale-search\u002F?s=search-query)\n- Configure higher number of search threads to parallelize disk reads. Default is `cpu_count - 1`, which is optimal for RAM-based search but may be too low for disk-based search. See [configuration reference](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fconfiguration\u002F?s=configuration-options)\n- If still saturated, scale out horizontally (each node adds independent IOPS)\n\n\n## What NOT to Do\n\n- Do not expect to optimize throughput and latency simultaneously on the same node\n- Do not use many small segments for throughput workloads (increases per-query overhead)\n- Do not scale horizontally when IOPS-bound without also upgrading disk tier\n- Do not run at >90% RAM (OS cache eviction = severe performance degradation)\n","# Scaling for Query Throughput (QPS)\n\nThroughput scaling means handling more parallel queries per second. \nThis is different from latency - throughput and latency are opposite tuning directions and cannot be optimized simultaneously on the same node.\n\nHigh throughput favors fewer, larger segments so each query touches less overhead.\n\n\n## Performance Tuning for Higher RPS\n\n- Use fewer, larger segments (`default_segment_number: 2`) [Maximizing throughput](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Foptimize\u002F?s=maximizing-throughput)\n- Enable quantization with `always_ram=true` to reduce disk IO [Quantization](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fquantization\u002F)\n- Use batch search API to amortize overhead [Batch search](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fsearch\u002Fsearch\u002F?s=batch-search-api)\n\n## Minimize impact of Update Workloads\n\n- Configure update throughput control (v1.17+) to prevent unoptimized searches degrading reads [Low latency search](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fsearch\u002Flow-latency-search\u002F)\n- Set `optimizer_cpu_budget` to limit indexing CPUs (e.g. `2` on an 8-CPU node reserves 6 for queries)\n- Configure delayed read fan-out (v1.17+) for tail latency [Delayed fan-outs](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fsearch\u002Flow-latency-search\u002F?s=use-delayed-fan-outs)\n\n\n\n## Horizontal Scaling for Throughput\n\nIf a single node is saturated on CPU after applying the tuning above, scale horizontally with read replicas.\n\n- Shard replicas serve queries from replicated shards, distributing read load across nodes\n- Each replica adds independent query capacity without re-sharding\n- Use `replication_factor: 2+` and route reads to replicas [Distributed deployment](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fdistributed_deployment\u002F?s=replication)\n\nSee also [Horizontal Scaling](..\u002Fscaling-data-volume\u002Fhorizontal-scaling\u002FSKILL.md) for general horizontal scaling guidance.\n\n\n## Disk I\u002FO Bottlenecks\n\nIf it is not possible to keep all vectors in RAM, disk I\u002FO can become the bottleneck for throughput. \nIn this case:\n\n- Upgrade to provisioned IOPS or local NVMe first. See impact of disk performance to vector search in [Disk performance article](https:\u002F\u002Fqdrant.tech\u002Farticles\u002Fmemory-consumption\u002F)\n- Use `io_uring` on Linux (kernel 5.11+) [io_uring article](https:\u002F\u002Fqdrant.tech\u002Farticles\u002Fio_uring\u002F)\n- In case of quantized vectors, prefer global rescoring over per-segment rescoring to reduce disk reads. Example in the [tutorial](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Ftutorials-operations\u002Flarge-scale-search\u002F?s=search-query)\n- Configure higher number of search threads to parallelize disk reads. Default is `cpu_count - 1`, which is optimal for RAM-based search but may be too low for disk-based search. See [configuration reference](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fconfiguration\u002F?s=configuration-options)\n- If still saturated, scale out horizontally (each node adds independent IOPS)\n\n\n## What NOT to Do\n\n- Do not expect to optimize throughput and latency simultaneously on the same node\n- Do not use many small segments for throughput workloads (increases per-query overhead)\n- Do not scale horizontally when IOPS-bound without also upgrading disk tier\n- Do not run at >90% RAM (OS cache eviction = severe performance degradation)\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fqdrant-scaling\u002Fscaling-qps",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill scaling-qps",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill scaling-qps",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill scaling-qps","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fqdrant-scaling\u002Fscaling-qps\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]