The performance of individual components, including CICS® Transaction Gateway, can affect
overall system performance.
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.
Threading model
A multithreaded model provides threads that are used for
handling network connections. Threads are also assigned to the requests
made by remote clients and the replies received from CICS.
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.
Configuring Windows for high network connection rates
When a TCP/IP socket is closed, it goes into TIME_WAIT state before
closing, for a period of time determined by the operating system.
A socket in TIME_WAIT state cannot be reused; this can limit the maximum
rate at which network connections can be created and disconnected.
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.