-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zero garbage JDBC tracing #35
Comments
See also p6spy/p6spy#436 |
This was referenced Apr 17, 2018
felixbarny
added a commit
to felixbarny/apm-agent-java
that referenced
this issue
May 14, 2018
closes elastic#35 Signed-off-by: Felix Barnsteiner <felix.barnsteiner@elastic.co>
Merged
felixbarny
added a commit
to felixbarny/apm-agent-java
that referenced
this issue
May 15, 2018
closes elastic#35 Signed-off-by: Felix Barnsteiner <felix.barnsteiner@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
P6spy allocates objects on each query:
https://github.com/p6spy/p6spy/blob/f9f852e895419a8adcda590618aec4ae47513cfe/src/main/java/com/p6spy/engine/wrapper/PreparedStatementWrapper.java#L59-L64
So investigate if p6spy could be easily modified to allow for object pooling or if we should rather implement our own JDBC wrapper. P6spy has an extensive test suite for all sorts of databases and application servers so it would be nice to leverage this.
The text was updated successfully, but these errors were encountered: