ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clinton Begin" <clinton.be...@gmail.com>
Subject Re: using java SortedSet instead of List for the resultMap
Date Thu, 04 Sep 2008 20:48:20 GMT
Don't set the cache to 1, that would be silly. :-)

Don't try to be too clever about it.  Just configure it simply and let it
work the way it works.

If you're trying to achieve some ultimate level of performance, then your
best bet is to cache outside of your persistence framework into something
like memcached or Coherence using your own business rules.  And of course
caching at the web tier is the biggest bang for your buck anyway.


On Thu, Sep 4, 2008 at 2:45 PM, zeppelin <shantanu.u@gmail.com> wrote:

> ' In a nutshell, cache lists, don't cache individual objects...' -  a
> little
> confusing
> If I'm ONLY caching a list, the size I need is only 1. Right ?
>        <cacheModel id="lruCache" type="LRU">
>                <flushInterval hours="24"/>
>                <property name="size" value="1" />
>        </cacheModel>
> If I decide to cache another object (POJO) and use the same cacheModel id
> (lruCache), I would need to change the size ( size="2" ) and the LRU
> algorithm will take care of expelling either of the two objects (POJO and
> list). Is this correct ?
> Sorry if all this has been answered before. I read the pdf a while back and
> still have some questions on caching.
> --
> View this message in context:
> http://www.nabble.com/using-java-SortedSet-instead-of-List-for-the-resultMap-tp19310126p19319593.html
> Sent from the iBATIS - User - Java mailing list archive at Nabble.com.

View raw message