Common performance issues

ADMINISTRATORON-PREMISE ONLY

Below is a list of factors that can significantly influence overall system performance, either positively or negatively depending on how they are implemented, configured, and maintained.

Factor	Effect on system performance
Lack of a proper maintenance plan	It is critical to have a maintenance plan defined that will keep your FactoryLogix database performing at its best. Instructions for setting up an appropriate maintenance plan can be found here: Database Best Practices.
Default page size	We recommend you leave the page size set to 20 and use the search feature to find the information. Setting the page size too large (500, for example), can cause long load times and timeouts returning data from the database. This setting is found in the FactoryLogix global options area of FactoryLogix Office (General category > Option Type: Display / GUI > Default Page Size).
Clustering indexes	Added in later versions of FactoryLogix, this option allows you to convert from using non-clustered indexes to clustered indexes. Clustered indexes organize data by a specific key and can significantly speed up data retrieval. The conversion option is found in FactoryLogix Server Management in the Database Utilities window.
Long wait times when logging in using Active Directory	Long waiting times when logging in when using Active Directory are usually caused by many Active Directory controllers being available and FactoryLogix needing to search for the correct one. This can be optimized by setting which Active Directory controllers to use in FactoryLogix global options (General category > Option Type: Active Directory > Active Directory Domain (optional). Multiple Active Directory controllers can be defined by using a “pipe” character as the separator: Example: dc=domaincontroller1\|dc=domaincontroller2\|dc=domaincontroller3
Switching Operator Interface templates	Frequent switching of Operator Interface templates (OIT) within the same operation of a manufacturing process can cause system performance issues. Each time the template is changed it must be reloaded from the database. We recommend you minimize switching Operator Interface templates as much as possible. See Operator Interface templates for more information.
Reporting service	When this option is defined in FactoryLogix global options (General category > Option Type: Reporting Service > Report Service Address), DataMiner data generation will be executed on the Report Scheduling Service rather than the Application Service which can increase system performance.
Multiple Application Service instances	If server resources allow, it is possible to run multiple instances of the Application Service on the same server. This allows the use of multiple instances and balancing the client load between them. It is recommended that each instance has at least 4GB of RAM available. This setting is found in Using Server Management (Service Settings window).
Display operation metrics	This is a feature you can turn on in FactoryLogix global options (Production Portal category > Option Type: Production Portal - Batch and Operation Selection > Display Operation Metrics) to display inbound and outbound quantities on the operations within a batch. This option is very resource intensive and will slow overall system performance—we recommend to not use this option.
SQL Server MAXDOP	Setting the SQL Server max degree of parallelism (MAXDOP) value too high may negatively impact query performance. The default value of 0 allows unrestricted use of all available processors; however, we recommend you set this value to match the number of NUMA nodes present. In environments without NUMA, an initial setting of 4 is a reasonable starting point. To configure the SQL Server MAXDOP setting for a specific database, right-click the database, select Properties, and open the Configurations section (a restart of the SQL Server service is required for changes to take effect).