Before you begin
For information on tuning the application server, see Tuning performance.Why and when to perform this task
To tune the gateway, implement as appropriate the performance enhancements described in the following list:
If you are passing an address for a WSDL file into the gateway, and the WSDL is stored locally, then use the file:///filename notation rather than drive letter:/filename because file:///filename is more performant.
The amount of storage (memory) that the gateway occupies depends upon the number of resources defined (channels, services, filters and so on). The complexity of the WSDL also affects the storage requirements for each Web service. If the resources you deploy to the gateway grow over time, you should review the heap size accordingly.
Although the Java heap storage requirement for each gateway-deployed service is small, if you deploy a large number of services or services with a large number of targets then you can significantly increase the heap space required to run the gateway efficiently. As well as the heap space required for the resource definitions, a large amount of additional heap space is occupied by resource objects instantiated when each service is invoked. The more deployed services or targets that are invoked, the more heap space is required by the gateway for the reusable elements of those services or targets.
The measurements in the following table estimate the Java heap storage space used by the gateway. These measurements were taken for a heap with these settings:
Resource | Storage space |
---|---|
Java heap requirements for the gateway with the following resources defined:
|
200KB |
Java heap requirements for each additional Web service target defined. |
1KB |
Java heap requirements for each Web service at runtime (that is, those components that are cached for future use and not eligible for garbage collection). |
1.2MB for first invocation 100KB for each additional target invoked |
These measurements are provided for illustrative purposes only. To review the gateway storage requirements for your environment, you should take your own measurements for that environment according to the formula described in the next paragraph.
For each Web service defined to the gateway, and for each service subsequently invoked, the Java heap working set is increased. The increase in heap occupancy is a function of base gateway requirements, plus the number of Web services defined, plus the number of unique Web services invoked during the lifetime of the gateway. This can be expressed as:
gateway_server_storage + n*def + rdef1 + n2*rdef2where: