openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karan Malhi" <karan.ma...@gmail.com>
Subject Re: Data + Query cache
Date Fri, 25 Aug 2006 21:00:01 GMT
I think the first time users are going to write simple applications while
evaluating . Will caching affect these kind of applications which have a
small amount of data to play around with?

On 8/24/06, Abe White <awhite@bea.com> 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.
>



-- 
Karan Malhi

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message