Enhance performance for "large" vaults

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,

Are you on v2026.1 already?

Hello Stéfane,

Can this warning/banner be suppressed so users dont see it, or the threshold increased? If so, which version of RDM/DVLS can accommodate this?

Thanks
Joe

Hello Stéfane

I somehow missed your reply. When we compare it to about a year ago, the performance is slower than before. For example opening an entry does take sometime and that was very fast before.
Also we had to split of a lot of credentials into a separate vault, as Devolutions Support says if we are over this limit, everything gets slow, and we can't have these credentials in the same vault.

This makes it a lot more complicated, to split credentials away from our customers, the same with the inventory, we have three vaults now instead of one. And I don't think we are such a big company, and don't know how others are handeling this.

Yes we ware on version 2026.1.15 and it's still the same.

Would be nice, to see that this gets addressed and that we could have 10'000 entries in one vault, without the need of splitting them up anymore.

Best regards
Patrick