So, I've got a huge stored procedure. Takes 20+ seconds to pull all sorts of counts about messages coming into the database that are all displayed on a single dashboard page. Obviously this time delay is unacceptable for the users.
I would love to use the hibernate query cache, but since messages are constantly coming in it would be constantly invalidating the cache and rerunning the query anyway. So, what if I don't mind if the query cache is out of date? Is there any way to turn off the UpdateTimestampsCache invalidation? Or, even better, use it as a way to tell how out of date the query cache is, but still pull the data out of the cache and not rerun the query?
|