Hi @Bharath_Meka1
Timeout in seconds for server is very high, especially when the servers are residing in the same internal network. When API-GW is running in the same network as the backend server or authentication/log server, we would have preferred a granularity in milliseconds.
Read Timeout is configured in seconds(max) after which a socket read attempt will get timed out. So it is better to be in seconds as part of the configurations ?
Any performance challenges are you incurring into if yes please mention?
From my observations, I see that API-GW opens a new socket connection for every log that it sends to the external endpoint server. After receiving a response from the endpoint server, it sends a FIN and closes the connection. When a new socket connection is created every time, a read timeout in seconds may be ok to have. However, since a new socket connection is created for every log sent to endpoint server it would have its own overhead, and can affect performance at high rate of traffic. If the same socket connections are reused for sending multiple logs, a read timeout in milliseconds would make more sense.
I have a follow up question:
Is there a configuration to change this behavior of API-GW? Meaning, can we configure the gateway to reuse socket connections instead of creating new ones every time?
