Results of Enterprise Content Management tuning

The results of the actions to tune the Enterprise Content Management (ECM) applications are now described.

Figure 1 shows the performance improvement after the ECM application tunings, described in the previous topics, are applied to the ECM Gateway and ECM application tier compared to the default settings.

The improvement for database indexing previously discussed does not count in this context, because it is not affecting the stable load phase from which the metric average response time is taken.

The transaction throughput rates were normalized against throughput number scored with no ECM application tuning at all. So the default settings normalized throughput rate was 1.0.

Figure 1 also shows the average response time in milliseconds for the transaction mix at a load level of 500 parallel virtual ICN users.

The throughput rate for the tuned environment increased by more than 30%, and the average response time reduced from 1500 milliseconds seconds to 275 milliseconds (a factor of 5.45).

The transaction throughput and response time improvements that resulted from this basic ECM application tuning were impressive. Most of the tuning settings were WAS parameters, which indicates that some relevant WAS parameters and their default values are only good enough for simple applications. More complex applications require a tuning of these WAS parameters to allow for maximum application performance and maximum utilization of the available server resources.