Tenant scaling

Skill mouadja02/skills/skills/llm-tooling/qdrant-scaling/scaling-data-volume/tenant-scaling

A curated collection of agent skills for your AI agents - engineering craft, prompt engineering, design, growth marketing, ...

Install

npx -y skills add mouadja02/skills --skill tenant-scaling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Guides Qdrant multi-tenant scaling

SKILL.md

2.7 KB, as published. Nobody here has run it

Attribution: Sourced from qdrant/skills by Qdrant.

What to Do When Scaling Multi-Tenant Qdrant

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.

Understand multitenancy patterns Multitenancy

Here is a short summary of the patterns:

Number of Tenants is around 10k

Use the default multitenancy strategy via payload filtering.

Read about Partition by payload and Calibrate performance for best practices on indexing and query performance.

Number of Tenants is around 100k and more

At this scale, the cluster may consist of several peers. To localize tenant data and improve performance, use custom sharding to assign tenants to specific shards based on tenant ID hash. This will localize tenant requests to specific nodes instead of broadcasting them to all nodes, improving performance and reducing load on each node.

If tenants are unevenly sized

If some tenants are much larger than others, use 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.

Need Strict Tenant Isolation

Use when: legal/compliance requirements demand per-tenant encryption or strict isolation beyond what payload filtering provides.

Multiple collections may be necessary for per-tenant encryption keys
Limit collection count and use payload filtering within each collection
This is the exception, not the default. Only use when compliance requires it.

What NOT to Do

Do not create one collection per tenant without compliance justification (does not scale past hundreds)
Do not skip is_tenant=true on the tenant index (kills sequential read performance)
Do not build global HNSW for multi-tenant collections (wasteful, use payload_m instead)