A Very Basic Question about Hibernate Profiler and the Hibernate 2nd level cache

[wabrit]

Apologies for what is an embarrassingly basic question, but I'm trying to figure out how much I can learn about 2nd level cache usage of my application through the Hibernate Profiler.

Does the profiler's session activity screen (showing SQL statements) only show those data operations deemed by Hibernate to require interaction with the database? 

In other words, if Hibernate deems that it can provide an entity, serve a query or follow an association from the 2nd level cache, what will be reported by the profiler to reflect this?

(I guess the question also applies to the session cache too; if Hibernate can serve an entity from the session cache rather than going to the database, will I see any session activity to reflect
this, or is it all subsumed under session statistics?)

Many thanks

Alan

[Oren Eini (Ayende Rahien)]

If Hibernate can serve a request from the session cache, you won't be seeing that, yes.

When you set the ProfilerQueryCacheFactory properly, it will detect 2nd level cache queries.