I have
<cache usage="read-only"/>

under a few <class>'es which represent good ol' code tables. I have a list of object of type A which refer to these "code objects" which are cached.

Yet, when I navigate from A to any of the code objects, hibernate generates SQL selects.

This makes the call horribly slow to traverse (thousands of selects just for a few hundred rows)

I use lazy="true" in the relation from class A to it's "code objects".

What's going on?

I tried going from session.find to session.iterate, but that dramatically slowed down the loop.

In my head, when I have a readonly <cache > under a <class>, Hibernate should always read from the cache, not issue selects'

Ummm. Anyone?

Umm - I cannot belive how slow find / iterate is.

The relationships are typically many-to-one... isn't those cached?

I tried to use JDBC and Hibernate to do the same thing. I'm using lazy sets and OSCache:

Getting 150 objects having 10 associations to other objects.

JDBC: 350 ms
Hibernate: 5 seconds
Hibernate, using iterate: 11 seconds

What on earth is going on???

When I don't close the session - the first call is slow, but the next call is superfast - I see from the SQL output that caching is effective.

But I have a session-per-request paradigm. Can I call disconnect() in that architecture???

I am only <cache> 'ing a few small tables, so that should be ok - right?