nababa
Reputation: 1321
JProfiler shows "unknown" JDBC calls take 40% of the time
I am using JProfiler to view all the JDBC calls in my application that's using Hibernate. It turns out that the top 2 hot spots are "unknown" and "select 1". Any ideas what they are?
Upvotes: 0
Views: 279
Answers (2)
Ingo Kegel
Reputation: 48090
Adding to Roger Lindsjö's answer, the "unknown" hot spot is a bug that has been fixed in JProfiler 7.0.1.
Upvotes: 0
Roger Lindsjö
Reputation: 11553
The "select 1" is a check to see if the connection is still valid. Can also be "select 1 from dual" or "select 1+1" depending on database used.
Upvotes: 2
Related Questions
- JPA: possible reason for high query execution time
- Profiling shows most of the time is spend in Hibernate loading classes - how to fix this?
- JProfiler : knowing which method is calling for java objects
- JProfiler: How do results from Hibernate profiling and JDBC profiling correlates?
- JPA/Hibernate 50% slower than using simple JDBC
- Is Hibernate's javassist supposed to cause this behaviour?
- Finding memory leak By JProfiler
- Can JProfiler tell me how long queries are taking?
- How can I debug this Hibernate/JPA slow query issue?
- Hibernate performance and memory leakage issues under profiler