[
https://issues.apache.org/jira/browse/OPENJPA-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Curtis closed OPENJPA-1329.
--------------------------------
Resolution: Not A Problem
Assignee: Rick Curtis
> But I don't know when the cache should be accessed to improve the
> performance? Is there any best practice for it ?
>From the user manual:
Most caches are of limited size. Pinning an identity to the cache ensures that
the cache will not kick the data for the corresponding instance out of the
cache, unless you manually evict it. Note that even after manual eviction, the
data will get pinned again the next time it is fetched from the store. You can
only remove a pin and make the data once again available for normal cache
overflow eviction through the unpin methods. Use pinning when you want a
guarantee that a certain object will always be available from cache, rather
than requiring a datastore trip.
Please reopen this JIRA if you have any additional questions.
Thanks,
Rick
> Looking for best practice for use DataCache API
> -----------------------------------------------
>
> Key: OPENJPA-1329
> URL: https://issues.apache.org/jira/browse/OPENJPA-1329
> Project: OpenJPA
> Issue Type: Question
> Components: datacache
> Affects Versions: 1.2.1
> Environment: windows/linux
> Reporter: Leilei Zhou
> Assignee: Rick Curtis
>
> I'm looking into OpenJPA's datacache. Config the cache enabled/disabled,
> cache size is not a problem and they do improve the performance. But from the
> guides, I can use OpenJPA's StoreCache/QueryCache extension to
> access(evict,pin...) the cache.
> But I don't know when the cache should be accessed to improve the
> performance? Is there any best practice for it ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
