Many factors or attributes impact OPPM sizing. These factors may affect Performance/hardware resources, but it again depends on the complexity of their implementation, the impact is not predictable mostly until later in the implementation process. This list may help as a guide for assessing needs and for avoiding implementation designs that create performance issues. The following set of identified attributes have been considered:
Note: In some cases, a single user can trigger millions of functions, so it entirely depends upon the type of dataset, type of operations, etc. But the below suggested / tested data set does not cover those type of scenarios. Processing of such huge amount of actions may take more time.
|
Name of the attributes |
Count |
|---|---|
|
Total number of categories |
5,000 |
|
Number of categories with horizontal functions |
1551 |
|
Number of categories with vertical functions |
4959 |
|
Number of categories that use the "today" function |
11 |
|
Total number of sub-items, items and portfolios |
31,941 |
|
Number of sub-items |
21,571 |
|
Number of items |
29,793 |
|
Data/row in cell history table |
21,638,853 |
|
Data/row in cell history log table |
1,354,215 |
|
Data/row in workflow instance audit log table |
797,230 |
Some of the other attributes that can affect OPPM performance and sizing needs are:
- Number of portfolios
- Number of categories with functions that walk the dependency tree(s)
- Number of categories with functions that access sub-items
- Number of categories with over-time functions
- Number of Query-Based portfolios set to periodically refresh
- Number of non-calculating portfolios
- Number of portfolios directly containing around 500 items
- Total number of dependency relations in system
- Highest number of dependencies on one item or portfolio
- Highest number of users in a group (directly or indirectly)
- Number of scorecards with more than 20 categories
- Number of tabs with more than 100 categories (directly or included in a table on the tab)
- Number of objects with individual security settings
- Number of general (e.g., not specific) alerts defined
- Number of categories set to “imported”
Typically these parameters may not be the same for all deployments; it entirely depends on the data set, environment and type of operations etc. Thus, huge variations in the parameters, skewed usage of OPPM will impact capacity requirements mentioned in this sizing guide. Moreover, these recommendations are based on the testing conducted under controlled environment where only OPPM application will be running on the servers.