We are writing to you from our development team to report and query a behavior we have evidenced when using the IBM.EntityFrameworkCore-lnx package version 7.0.0.400 in a production environment.
We have been working with this technology for approximately two years, and have recently started the production release of our .NET Core 7 based application deployed on Azure Kubernetes Service (AKS). However, we have identified inconsistent behavior in connection times to the DB2 database.
In particular, the OpenConnection statement exhibits variable latency: in some cases it is set to approximately 1 second, while in other cases it takes up to 30 seconds. This behavior occurs without a clear pattern, which makes it difficult to trace.
We would like to query whether this behavior may be related to:
Some internal aspect of the IBM.EntityFrameworkCore-lnx package,
Or some additional configuration recommended for containerized or AKS environments, specifically when working with DB2 connections.
We would greatly appreciate any guidance, recommendations or best practice guidelines you can provide to identify the root cause of this variable latency.