Parameter:
Server_Max_Possible_Trans_TimeShort description: Upper bound of transaction time (in 1/100 seconds) for calculating the availability index – above this value the index drops to 0 %.
Profile
Parameter | Server_Max_Possible_Trans_Time |
Category | Performance / Memory |
Component | Server |
Available since | 9.0.1 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | Integer in 1/100 s (default 5000 = 50 s) |
Description
The availability index (
Server.AvailabilityIndex) scales linearly between a minimum and a maximum transaction time. Server_Max_Possible_Trans_Time is the upper bound: if the average transaction time within the observation window exceeds this value, the server is considered “fully overloaded” (index = 0 %).The value is given in hundredths of a second – so 5000 corresponds to 50 seconds.
Example configuration
Server_Max_Possible_Trans_Time=3000
Notes & pitfalls
- Unit: 1/100 s, not milliseconds.
- Pairs with
Server_Min_Possible_Trans_Time,Server_Transinfo_Range,Server_MaxConcurrentTrans.
- A value that is too small makes the index drop to 0 % unrealistically often → cluster failover triggers more frequently.
- A value that is too large hides real problems.
- The change takes effect after a server restart.