Hi. Does anybody know if there is a collection limit? We have an application with approx. 20 master collections and 2 collections per user, resulting in approx. 8000 collections. When I use the Typsense Cloud Web UI or the Typesense Dashboard application to list/browser the collections, it results in my cluster going unhealthy due to an out of memory error 😓

Yeah that's fine. I've seen deployments with 100K collections. But at some point it's better to have a fixed number of collections and have it host multiple users. Rather than one per user because there's some fixed memory overhead for every collection which can be wasteful.

Would you consider the user-specific collection approach an anti-pattern then?

Yes, unless you plan to have less number of total users.

I see. Is there an official guideline with DOs and DONTs?

However we have fixed the memory issue with collection listing in recent versions

26.0 at the moment

Yes, try upgrading to 27.1

It's on our housekeeping todo list. Need to check the "Deprecations / behavior changes" sections of 27.0 and 27.1 first. But it seems there are no breaking changes.

You can test on a staging env before upgrading. Easy to downgrade as well.

I sure will, thanks 👍 Asking again: Is there an official guideline with DOs and DONTs? Like best practices and things to avoid like the many collections per user thingy?

Yes, but it's not a single list because of the breadth of the many topics involved. • https://typesense.org/docs/guide/organizing-collections.html#hierarchy (seems most relevant to you) • https://typesense.org/docs/guide/running-in-production.html#production-best-practices

Awesome! Thanks. Great support as always 👌