Performance Optimization#
This section describes some common settings recommendations regarding performance for Application and Database servers. A more thorough guide can be found in this link ⧉.
This section covers some tools and techniques to enhance the system performance. It includes the following sub-sections to address different types of computers:
- Application Server - how to fine tune the performance in the Application Server
- Database Server - how to optimize the performance of the Database Server
- Client Machines - how to optimize the performance of the User Interface on the client machines
Application Server#
Services and Operation#
To see if there are bottleneck Services or Operations in the system, the T_OperationHistory database table can be used.
This table provides the real time performance data for Services and Operations.
The table below lists the relevant table columns that should be checked.
| Column Name | Description |
|---|---|
| ServiceName | The name of the service |
| ServiceHistoryId | The transaction identifier |
| CreatedBy | The user who requested the service execution |
| OperationHistorySeq | The Operation call sequence |
| EntityTypeName | The name of the target operation EntityType |
| OperationName | The name of the executed operation |
| OperationStartTime | The date time of operation start execution |
| OperationEndTime | The date time of operation end execution |
Table: Table columns performance optimization
The OperationStartTime and OperationEndTime columns can be used to calculate the operation's time execution.
The standard report System/ServicePerformance provided in the default Critical Manufacturing installation can be used to access this information as shown in the next picture.
Info
If you notice transactions or services that do not have meet the expected performance or if the performance degrades over time, please contact Critical Manufacturing Support Team.
Database Server#
Info
This section contains material from Server Performance and Activity Monitoring ⧉
Monitoring and Tuning for Performance#
The goal of monitoring databases is to assess how a server is performing. Effective monitoring involves taking periodic snapshots of current performance to isolate processes that are causing problems, and gathering data continuously over time to track performance trends. SQL ServerTM and the Windows operating system provide utilities that let you view the current condition of the database and to track performance as conditions change.
Refer to the Monitoring and Tuning for Performance ⧉ for more information.
Performance Monitoring and Tuning How-to Topics#
There are a variety of tools and techniques that can be used to monitor Microsoft SQL ServerTM. Understanding how to monitor SQL ServerTM can help you:
- Determine whether performance improvements can be made
- Determine user activity to find out what queries users are issuing and who is connecting to SQL ServerTM
- Troubleshoot problems
- Test applications
Please refer to the article Performance Monitoring and Tuning How-to Topics ⧉ for more information.
Query Performance#
Before a Transact-SQL query, batch, stored procedure, trigger, prepared statement, or dynamic SQL statement begins execution on an instance of Microsoft SQL ServerTM, it is compiled into a query plan by the SQL Server Database Engine query optimizer. Then the plan is executed to produce a result-set. The compiled query plans are stored into a part of SQL ServerTM memory that is called the plan cache. Query performance can be analyzed to improve it by viewing query execution plans or by manipulating the way cached query plans are used by applications. The topics in this section contain information about how you can view and manipulate SQL Server Database Engine query plans to improve query performance.
Please refer to the article Query Performance ⧉ for more information.
Managing SQL Server Workloads with Resource Governor#
SQL ServerTM provides Resource Governor, a feature than you can use to manage SQL ServerTM workload and system resource consumption. Resource Governor enables you to specify limits on the amount of CPU and memory that incoming application requests can use.
Refer to the Managing SQL Server Workloads with Resource Governor ⧉ for more information.
Additional recommendations#
When running additional components associated to an MES installation (such as the ones described in Optional Components), the following recommendations also apply:
Power Options#
Power options can be accessed by typing powercfg.cpl. Servers must be configured for High Performance as shown in the picture below.
Network Adapters Power Management#
Network adapters can be configured in the Network and Sharing Center > Change Adapter Settings which can be accessed by typing ncpa.cpl. Disable the Allow computer to turn off this device to save power. option for all active network cards as shown in the next picture.
