Performance indicators and factors
The performance of CICS Transaction
Gateway can be measured to understand the factors that affect performance,
and to use the information provided to optimize that performance.
Benefits of using a 64-bit Gateway
If you run your Gateway with large numbers of clients and
large container payloads, for example, 2 MB or more, you should consider
using a 64-bit z/OS® Gateway.
Tuning the Gateway
You can tune the performance of your system by modifying
values such as the number of connection manager threads and worker
threads. Other values can also be modified to improve performance.
Tuning the JVM
Performance considerations related to Java include the
size of the Java heap, whether JIT (Just In Time compiler) is enabled,
and whether client applications are using persistent connections.
Tuning JEE
Because of the overheads associated with XA
transactions, the use of network and processor resources is higher
when using the XA transactional support provided by cicseci.rar with
the xasupport custom connection factory property set to on.
EXCI considerations
For EXCI workloads, CICS Transaction
Gateway and CICS must be configured
to ensure there are is not an EXCI pipe shortage.
IPIC considerations
When running the Gateway daemon under load and using IPIC
connected servers, you might need to increase the size of the JVM
heap for the Gateway daemon if performance problems are encountered.
Client applications
The parameters you set for your application can affect
performance.
Tracing
Full tracing of CICS Transaction
Gateway can degrade system performance and should not be used in a
production environment.
Performance monitoring tools
The performance monitoring tools provide a way of measuring
system performance characteristics such as transaction throughput
and processor usage.