cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Performance impact of measuring connection pool statistics?

AntonioSousa
Leader

It is recently possible to monitor database connection pool statistics:

https://www.dynatrace.com/news/blog/simplify-troubleshooting-with-ai-powered-insights-into-connectio...

In JBoss, it is stated that DataSource statistics are disabled by default to minimize performance impact. Is someone aware of how much performance impact there really is?

Antonio Sousa
2 REPLIES 2

JamesKitson
Dynatrace Leader
Dynatrace Leader

Redhat doesn't specify this anywhere. The only way to know for certain would be to run a test in your environment with that setting on the datasource enabled and disabled (not the extension, the Jboss setting itself).

In a very simple test I did I wasn't able to identify anything significant. In the below screenshot the first set of requests is with it enabled and the second is with it disabled. At most there might have been a <1% decrease with it disabled but that wasn't consistent.

Prod level traffic and application specific architecture of course can play a role too. I think they disabled it because in those earlier versions it would be silly to have it being collected by default even with the marginal overhead if it wasn't being used by anyone at all.

Thanks for the time & effort! (Some nice points are going your side )

I really did see it on Redhat's site:

Antonio Sousa