The following are some of the best practices recommended for improved performance:
- Do not create portfolios with thousands of items. Break these portfolios down into sub-portfolios that get rolled up into a portfolio of portfolios.
- On average servers, limit very large portfolios (up to 1,000 items) to one or two.
- Try to maintain an upper limit of 500 items in a single portfolio.
- These limitations hold true for static and Query-Based Portfolios (QBPs). Therefore, carefully examine the query definition of each QBP to ensure that these don't grow too large.
- Use non-calculating portfolios to organize thousands of items in one portfolio without incurring a negative impact to performance.
- The same limitations hold true for the number of dependencies on a single item or portfolio, but the performance impact is limited to functions walking the dependency tree(s).
- Scorecards with a large number of columns (typically >20 categories) and forms with multiple categories (>100 per tab) can also affect performance. Revisit your configuration choices and reduce complexity where practical.
- Run the Database Clean up Utilities on a regular basis (from the application console) to remove both duplicate and older cells from the database.
- Administrators can also reduce the size of the workflow instance audit log table by using a schedule job to cleanup workflow instances”.
- Finally, minimize user-driven actions and updates when there is a heavy load on the system. For example by processing large amounts of data during off-peak hours.