Database Probe distorts profiling results

[Jonas]

Looking into profiling results i see various Database Probe calls take significant amount of total time spent in data access layer. So if i see that my code spends 50% time in data access (hibernate my case) I can't rely on this deciding on optimization direction as bunch of this time is spent in Yourkit code, and actual time spent in data access may be much less than shown.
Can this be optimized in some way to reduce time spent in Yourkit code? I still need actual SQLs to be recorded
Using Yourkit EAP 14088

[Anton Katilin]

Yes, probes provide additional information but can add overhead. To minimize profiling overhead turn the probes off.

Anyway, let's investigate the overhead in your particular case.

Could you please provide a snapshot file demonstrating the problem.
Please capture it with the released version instead of the EAP build.