[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-github-qdrant-tenant-scaling":3,"mdc-nz3bbl-key":47,"related-org-github-qdrant-tenant-scaling":236,"related-repo-github-qdrant-tenant-scaling":407},{"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-tenant-scaling","scale multi-tenant Qdrant architectures","Guides Qdrant multi-tenant scaling. Use when someone asks 'how to scale tenants', 'one collection per tenant?', 'tenant isolation', 'dedicated shards', or reports tenant performance issues. Also use when multi-tenant workloads outgrow shared infrastructure.",{"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},"Multi-Tenant","multi-tenant",{"name":26,"slug":27,"type":15},"AI Infrastructure","ai-infrastructure",36978,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","2026-04-18T04:46:13.849317",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\u002Ftenant-scaling","---\nname: qdrant-tenant-scaling\ndescription: \"Guides Qdrant multi-tenant scaling. Use when someone asks 'how to scale tenants', 'one collection per tenant?', 'tenant isolation', 'dedicated shards', or reports tenant performance issues. Also use when multi-tenant workloads outgrow shared infrastructure.\"\n---\n\n# What to Do When Scaling Multi-Tenant Qdrant\n\nDo not create one collection per tenant. Does not scale past a few hundred and wastes resources. One company hit the 1000 collection limit after a year of collection-per-repo and had to migrate to payload partitioning. Use a shared collection with a tenant key.\n\n- Understand multitenancy patterns [Multitenancy](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F)\n\nHere is a short summary of the patterns:\n\n## Number of Tenants is around 10k\n\nUse the default multitenancy strategy via payload filtering.\n\nRead about [Partition by payload](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F?s=partition-by-payload) and [Calibrate performance](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F?s=calibrate-performance) for best practices on indexing and query performance.\n\n\n## Number of Tenants is around 100k and more\n\nAt this scale, the cluster may consist of several peers.\nTo localize tenant data and improve performance, use [custom sharding](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fdistributed_deployment\u002F?s=user-defined-sharding) to assign tenants to specific shards based on tenant ID hash.\nThis will localize tenant requests to specific nodes instead of broadcasting them to all nodes, improving performance and reducing load on each node.\n\n## If tenants are unevenly sized\n\nIf some tenants are much larger than others, use [tiered multitenancy](https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F?s=tiered-multitenancy) to promote large tenants to dedicated shards while keeping small tenants on shared shards. This optimizes resource allocation and performance for tenants of varying sizes.\n\n## Need Strict Tenant Isolation\n\nUse when: legal\u002Fcompliance requirements demand per-tenant encryption or strict isolation beyond what payload filtering provides.\n\n- Multiple collections may be necessary for per-tenant encryption keys\n- Limit collection count and use payload filtering within each collection\n- This is the exception, not the default. Only use when compliance requires it.\n\n\n## What NOT to Do\n\n- Do not create one collection per tenant without compliance justification (does not scale past hundreds)\n- Do not skip `is_tenant=true` on the tenant index (kills sequential read performance)\n- Do not build global HNSW for multi-tenant collections (wasteful, use `payload_m` instead)\n",{"data":48,"body":49},{"name":4,"description":6},{"type":50,"children":51},"root",[52,61,67,86,91,98,103,126,132,146,152,166,172,177,195,201],{"type":53,"tag":54,"props":55,"children":57},"element","h1",{"id":56},"what-to-do-when-scaling-multi-tenant-qdrant",[58],{"type":59,"value":60},"text","What to Do When Scaling Multi-Tenant Qdrant",{"type":53,"tag":62,"props":63,"children":64},"p",{},[65],{"type":59,"value":66},"Do not create one collection per tenant. Does not scale past a few hundred and wastes resources. One company hit the 1000 collection limit after a year of collection-per-repo and had to migrate to payload partitioning. Use a shared collection with a tenant key.",{"type":53,"tag":68,"props":69,"children":70},"ul",{},[71],{"type":53,"tag":72,"props":73,"children":74},"li",{},[75,77],{"type":59,"value":76},"Understand multitenancy patterns ",{"type":53,"tag":78,"props":79,"children":83},"a",{"href":80,"rel":81},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F",[82],"nofollow",[84],{"type":59,"value":85},"Multitenancy",{"type":53,"tag":62,"props":87,"children":88},{},[89],{"type":59,"value":90},"Here is a short summary of the patterns:",{"type":53,"tag":92,"props":93,"children":95},"h2",{"id":94},"number-of-tenants-is-around-10k",[96],{"type":59,"value":97},"Number of Tenants is around 10k",{"type":53,"tag":62,"props":99,"children":100},{},[101],{"type":59,"value":102},"Use the default multitenancy strategy via payload filtering.",{"type":53,"tag":62,"props":104,"children":105},{},[106,108,115,117,124],{"type":59,"value":107},"Read about ",{"type":53,"tag":78,"props":109,"children":112},{"href":110,"rel":111},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F?s=partition-by-payload",[82],[113],{"type":59,"value":114},"Partition by payload",{"type":59,"value":116}," and ",{"type":53,"tag":78,"props":118,"children":121},{"href":119,"rel":120},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F?s=calibrate-performance",[82],[122],{"type":59,"value":123},"Calibrate performance",{"type":59,"value":125}," for best practices on indexing and query performance.",{"type":53,"tag":92,"props":127,"children":129},{"id":128},"number-of-tenants-is-around-100k-and-more",[130],{"type":59,"value":131},"Number of Tenants is around 100k and more",{"type":53,"tag":62,"props":133,"children":134},{},[135,137,144],{"type":59,"value":136},"At this scale, the cluster may consist of several peers.\nTo localize tenant data and improve performance, use ",{"type":53,"tag":78,"props":138,"children":141},{"href":139,"rel":140},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Foperations\u002Fdistributed_deployment\u002F?s=user-defined-sharding",[82],[142],{"type":59,"value":143},"custom sharding",{"type":59,"value":145}," to assign tenants to specific shards based on tenant ID hash.\nThis will localize tenant requests to specific nodes instead of broadcasting them to all nodes, improving performance and reducing load on each node.",{"type":53,"tag":92,"props":147,"children":149},{"id":148},"if-tenants-are-unevenly-sized",[150],{"type":59,"value":151},"If tenants are unevenly sized",{"type":53,"tag":62,"props":153,"children":154},{},[155,157,164],{"type":59,"value":156},"If some tenants are much larger than others, use ",{"type":53,"tag":78,"props":158,"children":161},{"href":159,"rel":160},"https:\u002F\u002Fsearch.qdrant.tech\u002Fmd\u002Fdocumentation\u002Fmanage-data\u002Fmultitenancy\u002F?s=tiered-multitenancy",[82],[162],{"type":59,"value":163},"tiered multitenancy",{"type":59,"value":165}," to promote large tenants to dedicated shards while keeping small tenants on shared shards. This optimizes resource allocation and performance for tenants of varying sizes.",{"type":53,"tag":92,"props":167,"children":169},{"id":168},"need-strict-tenant-isolation",[170],{"type":59,"value":171},"Need Strict Tenant Isolation",{"type":53,"tag":62,"props":173,"children":174},{},[175],{"type":59,"value":176},"Use when: legal\u002Fcompliance requirements demand per-tenant encryption or strict isolation beyond what payload filtering provides.",{"type":53,"tag":68,"props":178,"children":179},{},[180,185,190],{"type":53,"tag":72,"props":181,"children":182},{},[183],{"type":59,"value":184},"Multiple collections may be necessary for per-tenant encryption keys",{"type":53,"tag":72,"props":186,"children":187},{},[188],{"type":59,"value":189},"Limit collection count and use payload filtering within each collection",{"type":53,"tag":72,"props":191,"children":192},{},[193],{"type":59,"value":194},"This is the exception, not the default. Only use when compliance requires it.",{"type":53,"tag":92,"props":196,"children":198},{"id":197},"what-not-to-do",[199],{"type":59,"value":200},"What NOT to Do",{"type":53,"tag":68,"props":202,"children":203},{},[204,209,223],{"type":53,"tag":72,"props":205,"children":206},{},[207],{"type":59,"value":208},"Do not create one collection per tenant without compliance justification (does not scale past hundreds)",{"type":53,"tag":72,"props":210,"children":211},{},[212,214,221],{"type":59,"value":213},"Do not skip ",{"type":53,"tag":215,"props":216,"children":218},"code",{"className":217},[],[219],{"type":59,"value":220},"is_tenant=true",{"type":59,"value":222}," on the tenant index (kills sequential read performance)",{"type":53,"tag":72,"props":224,"children":225},{},[226,228,234],{"type":59,"value":227},"Do not build global HNSW for multi-tenant collections (wasteful, use ",{"type":53,"tag":215,"props":229,"children":231},{"className":230},[],[232],{"type":59,"value":233},"payload_m",{"type":59,"value":235}," instead)",{"items":237,"total":406},[238,252,270,286,300,316,330,342,354,366,382,394],{"slug":239,"name":239,"fn":240,"description":241,"org":242,"tags":243,"stars":28,"repoUrl":29,"updatedAt":251},"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},[244,245,246,249,250],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":247,"slug":248,"type":15},"Capacity Planning","capacity-planning",{"name":20,"slug":21,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:16.349561",{"slug":253,"name":253,"fn":254,"description":255,"org":256,"tags":257,"stars":28,"repoUrl":29,"updatedAt":269},"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},[258,261,262,265,268],{"name":259,"slug":260,"type":15},"Data Engineering","data-engineering",{"name":20,"slug":21,"type":15},{"name":263,"slug":264,"type":15},"ETL","etl",{"name":266,"slug":267,"type":15},"Performance","performance",{"name":17,"slug":18,"type":15},"2026-04-18T04:46:02.766357",{"slug":271,"name":271,"fn":272,"description":273,"org":274,"tags":275,"stars":28,"repoUrl":29,"updatedAt":285},"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},[276,279,280,283,284],{"name":277,"slug":278,"type":15},"Cost Optimization","cost-optimization",{"name":20,"slug":21,"type":15},{"name":281,"slug":282,"type":15},"Observability","observability",{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:01.525023",{"slug":287,"name":287,"fn":288,"description":289,"org":290,"tags":291,"stars":28,"repoUrl":29,"updatedAt":299},"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},[292,293,294,295,296],{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},{"name":297,"slug":298,"type":15},"Search","search","2026-04-18T04:46:10.126667",{"slug":301,"name":301,"fn":302,"description":303,"org":304,"tags":305,"stars":28,"repoUrl":29,"updatedAt":315},"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},[306,309,312,313,314],{"name":307,"slug":308,"type":15},"Debugging","debugging",{"name":310,"slug":311,"type":15},"Monitoring","monitoring",{"name":281,"slug":282,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:06.450784",{"slug":317,"name":317,"fn":318,"description":319,"org":320,"tags":321,"stars":28,"repoUrl":29,"updatedAt":329},"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},[322,323,324,325,326],{"name":26,"slug":27,"type":15},{"name":310,"slug":311,"type":15},{"name":281,"slug":282,"type":15},{"name":17,"slug":18,"type":15},{"name":327,"slug":328,"type":15},"SRE","sre","2026-04-18T04:46:05.217192",{"slug":331,"name":331,"fn":332,"description":333,"org":334,"tags":335,"stars":28,"repoUrl":29,"updatedAt":341},"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},[336,337,338,339,340],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":247,"slug":248,"type":15},{"name":20,"slug":21,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:07.684464",{"slug":343,"name":343,"fn":344,"description":345,"org":346,"tags":347,"stars":28,"repoUrl":29,"updatedAt":353},"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},[348,349,350,351,352],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},"2026-04-18T04:46:08.905219",{"slug":355,"name":355,"fn":356,"description":357,"org":358,"tags":359,"stars":28,"repoUrl":29,"updatedAt":365},"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},[360,361,362,363,364],{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},{"name":297,"slug":298,"type":15},"2026-04-18T04:46:11.371326",{"slug":367,"name":367,"fn":368,"description":369,"org":370,"tags":371,"stars":28,"repoUrl":29,"updatedAt":381},"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},[372,375,378,379,380],{"name":373,"slug":374,"type":15},"Analytics","analytics",{"name":376,"slug":377,"type":15},"Data Quality","data-quality",{"name":307,"slug":308,"type":15},{"name":17,"slug":18,"type":15},{"name":297,"slug":298,"type":15},"2026-04-18T04:46:17.579894",{"slug":383,"name":383,"fn":384,"description":385,"org":386,"tags":387,"stars":28,"repoUrl":29,"updatedAt":393},"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},[388,389,390,391,392],{"name":373,"slug":374,"type":15},{"name":20,"slug":21,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},{"name":297,"slug":298,"type":15},"2026-04-18T04:46:03.987332",{"slug":395,"name":395,"fn":396,"description":397,"org":398,"tags":399,"stars":28,"repoUrl":29,"updatedAt":405},"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},[400,401,402,403,404],{"name":26,"slug":27,"type":15},{"name":373,"slug":374,"type":15},{"name":13,"slug":14,"type":15},{"name":17,"slug":18,"type":15},{"name":297,"slug":298,"type":15},"2026-04-18T04:46:18.812306",45,{"items":408,"total":465},[409,417,425,433,441,449,457],{"slug":239,"name":239,"fn":240,"description":241,"org":410,"tags":411,"stars":28,"repoUrl":29,"updatedAt":251},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[412,413,414,415,416],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":247,"slug":248,"type":15},{"name":20,"slug":21,"type":15},{"name":17,"slug":18,"type":15},{"slug":253,"name":253,"fn":254,"description":255,"org":418,"tags":419,"stars":28,"repoUrl":29,"updatedAt":269},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[420,421,422,423,424],{"name":259,"slug":260,"type":15},{"name":20,"slug":21,"type":15},{"name":263,"slug":264,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},{"slug":271,"name":271,"fn":272,"description":273,"org":426,"tags":427,"stars":28,"repoUrl":29,"updatedAt":285},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[428,429,430,431,432],{"name":277,"slug":278,"type":15},{"name":20,"slug":21,"type":15},{"name":281,"slug":282,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},{"slug":287,"name":287,"fn":288,"description":289,"org":434,"tags":435,"stars":28,"repoUrl":29,"updatedAt":299},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[436,437,438,439,440],{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},{"name":297,"slug":298,"type":15},{"slug":301,"name":301,"fn":302,"description":303,"org":442,"tags":443,"stars":28,"repoUrl":29,"updatedAt":315},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[444,445,446,447,448],{"name":307,"slug":308,"type":15},{"name":310,"slug":311,"type":15},{"name":281,"slug":282,"type":15},{"name":266,"slug":267,"type":15},{"name":17,"slug":18,"type":15},{"slug":317,"name":317,"fn":318,"description":319,"org":450,"tags":451,"stars":28,"repoUrl":29,"updatedAt":329},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[452,453,454,455,456],{"name":26,"slug":27,"type":15},{"name":310,"slug":311,"type":15},{"name":281,"slug":282,"type":15},{"name":17,"slug":18,"type":15},{"name":327,"slug":328,"type":15},{"slug":331,"name":331,"fn":332,"description":333,"org":458,"tags":459,"stars":28,"repoUrl":29,"updatedAt":341},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[460,461,462,463,464],{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":247,"slug":248,"type":15},{"name":20,"slug":21,"type":15},{"name":17,"slug":18,"type":15},15]