Let’s talk briefly about concurrent user access to the vRealize Operations UI.

There is no hard guidance on the maximum concurrent users per node. It is considered that four users is the recommended maximum per node, irrespective of node size, but depending on the use case, that number may be a lot higher. 

Let's give an example:

Let’s say you have 100 dashboards that your vRealize Operations users, constantly monitor. This means the vRealize Operations UI needs to load, build up, and populate those dashboards with information from the databases and the GemFire caching layer for each user viewing them. Four users are considered to be the maximum number of concurrent users before degradation in user performance may start to take place. Let's say a fifth or sixth user logs in. They will still be able to log in, but they may notice performance degradation, such as slow UI responsiveness.

On the other hand, you may have 20 or 30 concurrent vRealize Operations users where each of them only has permissions and views on only a limited subset of dashboards. In this case, you may not see performance degradation at all.

As we said, these are just example numbers, there is no hard guidance on this. So, make sure to plan user access accordingly. Try to stick to a tight group of vRealize Operations users and give them permissions only to dashboards that are relevant to their business unit or role.