My Oracle Support Banner

Performance Drop On Tuxedo Application Server, Under High Load, When SVCTIMEOUT Is Configured (Doc ID 2209131.1)

Last updated on MAY 13, 2022

Applies to:

Oracle Tuxedo - Version 12.1.3 and later
Information in this document applies to any platform.


In Tuxedo applications a performance drop has been observed in the processing time of one Tuxedo application server named "serverA". Previously this "serverA" needed an estimated 2ms for completing a transaction. Once the SVCTIMEOUT parameter is "serverA" needs around 25ms and is losing time when communicating with another Tuxedo application server named "serverB". Estimated that "serverA" received an answer from "serverB" after 23ms.("serverA" is doing a service request named "svcB" to "serverB")
The Tuxedo ubb configuration SVCTIMEOUT parameter is set for all services in the "serverB" application servers.

The performance degradation was as follows:
1. With only 1 "serverA" didn't have any waiting time but 1 "serverA" is not enough to reach the required performance.
2. With 2 "serverA"s had a very small wait time (4ms).
3. With 8 "serverA"s, the waiting time was only 10ms (but performance kept the same).
4. When use 16 "serverA" servers, average wait time from response from the "serverB" (for "svcB" request) is around 25ms.
5. When using 32 converters the average waiting time is now increase to 50ms.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.