Memory Optimization

The Memory Optimization tab is used to configure the Transaction Server image and execution options to use on a Mitsubishi MESInterface IT node. This tab is not available for other products.

The parameters are as follows:

Parameter Description
Throughput Specifies how many resources are pre-initialized in the Transaction Server component. The simple equation is more pre-initialized resources results in less available memory.
The options are:
  • High Capacity - This is the default option. The High Capacity option results in a higher number of pre-initialized resources in the Transaction Server to process Transaction actions. This is recommended if you are using several transports to access enterprise applications or you are expecting a transport to go into and out of Store and Forward frequently due to a bad enterprise application connection. When resources are pre-initialized you will reduce your chances of getting an Out of Memory exception when connections to enterprise applications are established. This option will use more memory than the Low Capacity option.
  • Low Capacity - The Low Capacity option results in a lower number of pre-initialized resources in the Transaction Server to process Transaction actions. This is recommended if you are using one transport to access the endpoint enterprise application, or more than one transport that have a stable enterprise application connection (you do not anticipate going into and out of Store and Forward frequently). This option will use less memory than the High Capacity option.
Enterprise Access Specifies the Transaction Server image to use. The options are a trade off between additional optimized code paths for faster execution times versus additional available memory for the application.
The options are:
  • Standard - This is the default option. The Standard option has optimized code paths for several databases, so transaction execution times to all databases are relatively fast. However, this option uses more system memory than the other options.
  • Optimized for Oracle - The Optimized for Oracle option has the code path for Oracle databases optimized. It uses less system memory than the Standard option.
    Note that transaction execution times for other database servers such as SQL Server or DB2 will be 6 times slower.
  • Optimized for SQL Server - The Optimized for SQL Server option has the code path for SQL Server databases optimized. It uses less system memory than the Standard option.
    Note that transaction execution times for other database servers such as Oracle or DB2 will be 6 times slower.
  • Optimized for IBM (DB2 and SIB) - The Optimized for IBM (DB2 and SIB) option has the code paths for IBM DB2 databases or SIB transports optimized. It uses less system memory than the Standard option.
    Note that transaction execution times for other database servers such as Oracle or SQL Server will be 6 times slower.
  • Optimized for IFS - The Optimized for IFS option is mandatory when the system will access the IFS cloud server. The Standard setting does not contain the necessary optimizations to speed up IFS cloud server access. When this option is selected, transaction execution times for other end point enterprise applications will be up to 6 times slower.
Description The Description box provides an explanation of the options for the two parameters.

Select the Save button to save any changes to the parameters.

After making changes and saving them, the CCPU must be restarted for the changes to take effect.

Memory optimization summary

Suppose you selected the Optimized for SQL Server option from the Enterprise Access parameter. When the trigger executes, an Insert transaction will take approximately 200 milliseconds to complete to an SQL Server database. Likewise, the Insert transaction will also take the same 200 milliseconds to execute using the Standard option.
However, if the target is an Oracle database and the option is Optimized for SQL Server, the Insert transaction will take about 1.2 seconds to complete. This is because the Transaction Server image configured, Optimized for SQL Server, does not have the code path optimization for the Oracle database.
The trade off is that the system will have more available memory using Optimized for SQL Server when compared to the Standard option.

The following table shows this analysis:

Option SQL Server database Oracle database DB2 database Available memory
Standard 200 ms 200 ms 200 ms Same
Optimized for SQL Server 200 ms 1.2 sec 1.2 sec More
Optimized for Oracle 1.2 sec 200 ms 1.2 sec More

If you only use a SQL Server database in your application, then you can have the benefit of more available memory by choosing the Optimized for SQL Server option.
However, if your applications uses both an SQL Server database and an Oracle database in your final solution, then you should choose the Standard option.