Enhance performance for "large" vaults
1 vote
Hello
It's 2026 and we have databases which can handle millions of entries with no problem.
In RDM when we have 4000 entries, we get messages, that the vault has a large number of entries and the performance is impacted.
Is that something that could be enhanced in a next version, instead of bringing many new features. ;-) We think 4000 entries, are not to many today.
All Comments (2)
Hi,
The comparison with “modern databases handling millions of rows” isn’t quite apples to apples.
RDM isn’t just storing flat data. Every entry sits in a hierarchy, inherits permissions, and requires validation at multiple levels. That adds overhead that a simple table lookup in a database doesn’t have.
The 4,000 entry message is not a hard limit, it’s more of a guideline. Plenty of environments run well beyond that. We’ve seen setups with 10,000+ entries per vault, and internally there are tests with 20,000+ entries under different structures, including extreme cases like very deep folder hierarchies.
In practice, performance depends much more on how the data is structured than the raw number of entries.
For example:
- Large numbers of entries at the root level can slow things down
- Deep or complex permission inheritance can add overhead
- Certain data sources or configurations can be more expensive to load
So the real question is: are you actually seeing performance issues, or just the warning?
If you are seeing slowdowns, the best next step is to run the profiler and share a trace. In most cases, the bottleneck ends up being data-related or configuration-specific, and once identified it can usually be improved.
If everything is running fine, the warning can generally be taken as informational rather than a sign that something is broken.
Best regards,
Stéfane Lavergne
Are you on v2026.1 already?
Stéfane Lavergne