This section provides estimates of server configurations for varying numbers of named users, licensed and concurrent users. A named user is a user who has an account with the system but may not currently be logged in. A concurrent user is a user currently logged into the system.
This document assumes:
- The maximum number of concurrent users at any given time is around 20% of the named users. The hardware sizing is based on the maximum concurrent users estimated for each deployment category. Named users counts can be used to estimate concurrent users in cases where concurrent user counts are not available.
- Users are continuously performing actions and use 60 seconds of think time (intervals between interactions)
Based on a typical production environment and respective loads, OPPM deployments can be categorized into three categories: Small, Medium, and Large. Tests were conducted for moderate and large datasets, and the maximum recommended number of concurrent users is listed in the table below. However, the recommended user counts will not be the same for all deployments; it depends entirely on the data set, environment, type of operations, and so on. Moreover, these recommendations are based on the testing conducted under a controlled environment where OPPM is the sole application running on the servers.
Attributes | XSmall | Small | Medium | Large |
|---|---|---|---|---|
Number of Named Users | less than 100 | 100 - 250 | 251 - 750 | 751 - 1250 |
Maximum concurrent users (with an average of 60 seconds think time) | 20 | 50 | 100 | 200 |
Note: In some cases, a single user can trigger millions of functions; therefore, it entirely depends upon the type of data set, type of operations, and so on. The following suggested / tested data set does not cover those type of scenarios. Processing of such huge amount of actions may take more time.