Connection Pooling
Hi Azure Cosmos Db Team, Is there any best practices to identify if there is connection pooling happening with Cosmos Db JAVA SDK? I see for pointread call the average duration in ms is well around 10 ms from comsos db diagnostic logs but in app insights for the Microsoft.DocumentDb call duration for the cosmos db interaction ( for doing pointread) varies considerably and sometimes reaches around 600 ms especially as number of threads( 5-600 threads step by step in our case) are increased in load testing ? I am suspecting this is happening as the sdk is trying to open a new connection as threads increases and this results in increased latency for "some" requests? I see that for the first call there is a login.microsoftonline.com call happening before doing the actual read in cosmos db but cannot see this call in all the ones with higher latency from app insights probably due to sampling in app insights? We are using direct connection mode in sdk. The direct connection configuration parameters currently used are based on the below documentation. https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/tune-connection-configurations-java-sdk-v4?tabs=api-async With Regards, Nitin Rahim