This document provides recommendations for server hardware and network architecture for a PTC Integrity Implementation. It provides supplementary material to the already available Integrity System Guidelines PDF available from here. It is highly recommended that readers review the Integrity System Guidelines as a prerequisite before proceeding.
It is a challenge to define a precise hardware configuration that will provide a targeted level of performance for a specific number of users without a detailed usage profile of these users. Although the total number of potential users needs to be considered, a more important criterion for Integrity Server scalability is the number of concurrent, or simultaneously active, users and what operations these different users are performing. Different areas of functionality will require varied server resources and may experience different performance bottlenecks. Although the Integrity server will almost certainly draw resources from all of the areas listed below for many operations, the main resource required for various areas of functionality is as follows:
- DB Usage: Item Branching, Historical Operations (Item Views, Computations and Reports), Item Revisioning, Historical operations
- Server Memory Usage: Run Reports, Charts & Dashboards, Web UI usage
- Server Disk I/O Usage: Member Based Source/Configuration Management Commands, Federated Server Architecture Caching
- Network Usage: Large File Operations in Source (Check-outs or Check-ins) , Federated Server Architecture Caching
- LDAP Usage: Authentication, Refreshing User and Group Caches
This document’s primary focus is on the immediate deployment of Workflows and Documents functionality; however, consideration for future inclusion of Configuration Management functionality in the Solution is also included.
