Hardware Recommendations
This section describes the recommended hardware specifications which are needed for Workflow to perform well.
The following table provides general guidelines for hardware recommendations based on sizing specifications.
Project Specification | Small System | Medium System* | Large System* |
---|---|---|---|
Equipment Model Objects | 0 – 500 | 500 – 2,500 | 2,500 + |
Equipment Model Properties | 0 – 5,000 | 5,000 – 500,000 | 500,000 + |
Material Definitions | 0 – 1,000 | 1,000 – 10,000 | 10,000 + |
Material Lots | 0 – 1,000 | 1,000 – 5,000 | 5,000 + |
Production Model Objects | 0 – 500 | 500 – 1,000 | 1,000 + |
Production Variables | 0 – 5,000 | 5,000 – 10,000 | 10,000 + |
Number of Workflows | 0 – 100 | 100 – 1,000 | 1,000 + |
Running Workflows | 0 – 50 | 50 – 500 | 500 + |
Concurrently Executing Workflows** | 0 – 5 | 5 – 25 | 25 + |
Configured Events | 0 – 50 | 50 – 500 | 500 + |
Events Triggering per Hour | 0 – 15 | 15 – 100 | 100 + |
Work Requests in System | 0 – 100 | 100 – 1,000 | 1,000 + |
Active Work Requests | 0 – 25 | 25 – 500 | 500 + |
Active Clients | 1 – 25 | 25 – 100 | 100 + |
Recommended Server RAM | 8 GB | 16 GB | 32 GB |
Recommended Server CPUs | 2 CPUs @ 3GHz | 4 CPUs @ 3GHz | 8 CPUs @ 3GHz |
*Many systems do not use all of the capabilities of Workflow, so some projects may match some specifications in the small system column with other specifications in the medium or large system column. Choose the column that more closely matches the targeted system.
**Any running workflow that is waiting for user input in a task form can be considered paused and is considered to be a running workflow but not an executing workflow.
Additional Factors for Hardware Recommendations
Special Application Factors
Server recommendations may need to be increased when the application uses intensive processing or significant disk access. Examples of these scenarios include reading and parsing data files from disk, custom logging or writing to output data files, advanced mathematics in code activities, custom service providers, communicating with third party products, and so on.
SQL Server on the Workflow Server
The hardware recommendations above are for servers where the SQL Server is not on the Workflow server system. If you choose to run SQL Server on the Workflow server, then you must add RAM and CPUs to the recommended amounts.
Running on a Virtualized Machine
The hardware recommendations above are for a server that is not running in a virtualized environment. For servers that are running in a virtualized environment such as a VMWare or Hyper-V image, the recommended amounts must be exclusively allocated to the server image and have as much available physical resources on the virtualization server. For example, if a server needs 8GB of RAM, then that much RAM must be allocated to the image, and the virtualization server must have 8GB of physical RAM available for that image. If the image runs out of physical RAM on the virtualization server, performance degrades significantly.
Running Other Applications
Additional Recommendations for the SQL Server Machine
- SQL database: RAID 0+1, RAID 1 or RAID 5
- SQL transaction logs: RAID 0+1 or RAID 1, and should be a separate physical device
- SQL tempdb: RAID 0+1 or RAID 1
- SQL indexes: RAID 0+1 or RAID 1
- Back-ups: RAID 0 (no fault tolerance, but faster writes) or RAID 5
- SQL Server machine: 4 GB RAM (required minimum)
- Use Windows Authentication only. For information on how to connect to a remote SQL Server instance using Windows Authentication, please see Configure Windows Authentication for Workflow in the Workflow Help documentation.
- Exclude the database files from anti-virus scanning
- Use multiple processors for every installation
- Enable the default backup job or create a maintenance plan
- For tempdb, the number of files configured should be based on the number of processors that the server has (for more information, see Optimizing tempdb Performance)
Other Performance Considerations
- Networking throughput between Workflow server and client
- Networking throughput between Workflow server and SQL Server
- Data throughput between the Workflow server and data sources such OPC servers, Historian, iFIX, and CIMPLICITY.
- The number of client instances active on a single client machine