Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Most applications should be using a connection pool that has a limited number of connections. The connections returned from that pool should be wrapped in a way that code in
opentelemetry-java-instrumentation/instrumentation/jdbc/library/src/main/java/io/opentelemetry/instrumentation/jdbc/internal/JdbcUtils.java
Line 24 in bfeb482
DbInfo
instances. If application does not use a connection pool or we are unable to unwrap connection to get the original one that already hasDbInfo
attached we'll end up with a large number ofDbInfo
instances which all contain the same data. I have a heap dump that has a bit under a millionDbInfo
instances consuming slightly less than 500mb.