openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Noll <>
Subject Re: Data + Query cache
Date Thu, 24 Aug 2006 21:34:03 GMT
I found this 

but I was looking for some documentation about what the default cache 
configuration settings would be, and I'm not seeing it there.

The point you made about the behavior being less obvious is not that big 
a deal to me.... I assume that if someone isn't sure what's going on, 
they'll turn on DEGUG or TRACE level logging, and see some kind of 
message like :

"To let you know, this wasn't retrieved from the database, we still had 
the object in the cache, so that's where it is coming from.  By the way, 
if you actually want the performance gains, you better set your logging 
level a little higher."

Two concern I would have would be:

1) How much memory would the default 'cache on' setting consume?  Are 
people going to easily receive OOM errors with the default settings?  (I 
doubt it, but thought it should be mentioned.)
2) What's the default concurrency strategy?  My wife and I making an ATM 
withdrawal or deposit at the same time makes me nervous the farther away 
from transactional we get.

Just some thoughts...

Abe White wrote:
> How does the list feel about turning the L2 data and query caches on 
> by default?  Traditionally, Kodo always left them off by default, 
> primarily because they required a "performance pack" license to run.
> One downside of turning the caches on by default is that OpenJPA's 
> behavior becomes less obvious.  Actions like refresh() that users 
> might expect to hit the DB will often be intercepted by the cache 
> instead.  It might confuse some users.  Also, OpenJPA will suck up 
> more memory with the cache on than with it off.  And certain very 
> naïve tests that don't utilize caching can be slightly slower.
> Personally, I think providing new users / evaluators with potentially 
> vastly increased performance outweighs the 
> downsides._______________________________________________________________________ 
> Notice:  This email message, together with any attachments, may contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted  and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.

View raw message