There are different use cases for this I guess. I believe your use case
involves a single long lived context which exists primarily because of the
large cache attached to it.
My use case is for lots of very short lived contexts with data that I
really want to stay cached for the entire very short
> The docs suggest(ed?) that local cache was local to that object context, but
> it really ends up being global.
What is real? :) https://www.youtube.com/watch?v=-niPJMSeh34
It is local from the app perspective. Query cache is a common memory region
that can be used by multiple contexts. Just
I agree, I had the same issue. The docs suggest(ed?) that local cache was
local to that object context, but it really ends up being global. I had a
couple of Caffeine solutions in place too that did bind it closer to the
EC. I've since scrapped that (not sure why) and it least ties the cache to
My main problem was that the docs imply that locally cached things are tied
to a single object context, giving the expectation that when the context
goes away the locally cached things go away too. This is only superficially
true -- indeed you can't access them anymore, but the objects are still in
Yeah, LRU caches are prone to individual cache entry size fluctuations. With
large active caches this averages out (more or less), but is still an issue.
Somehow I overlooked Caffeine. Looks interesting. Let me try to switch a few
projects.
Andrus
> On Apr 12, 2018, at 6:45 AM, Aristedes Mani
On 11/4/18 11:28pm, Andrus Adamchik wrote:
Also EhCache may actively remove expired items (?), but OSCache certainly did
not, and it was not a problem either, also because of maxsize/LRU.
Actually that's a problem in EHcache that had us leave it and use
Caffeine instead. EHCache only tries to
Not if it is marked as expired. In which case the cache on access will behave
as if the object is not there at all.
Andrus
> On Apr 11, 2018, at 9:03 PM, Lon Varscsak wrote:
>
> If an object stays in this cache though, don't I get potentially stale
> objects back later?
>
> On Wed, Apr 11, 2
If an object stays in this cache though, don't I get potentially stale
objects back later?
On Wed, Apr 11, 2018 at 6:28 AM, Andrus Adamchik
wrote:
>
>
> > On Apr 10, 2018, at 6:47 PM, John Huss wrote:
> >
> > 1) Data written to the Local query cache will survive the lifetime of the
> > ObjectCo
> On Apr 10, 2018, at 6:47 PM, John Huss wrote:
>
> 1) Data written to the Local query cache will survive the lifetime of the
> ObjectContext. If the cache group it is written to does not have an
> explicit expiration time, then it will stay in the cache forever until you
> run out of memory.
I've started using the Query Cache more in some apps and I have noticed a
problem with the way it uses memory.
BACKGROUND
Cayenne has two versions of the Query Cache - Local and Shared. The shared
cache data is available to all ObjectContexts. The Local cache data is
available only to the same Ob
10 matches
Mail list logo
