Cache per item usage meta data? #146
Replies: 9 comments
-
|
After diving into the source I think I have found that the statistics are held in LocalCache.Entry that I can get through the backing map that requires a deprecated method to access .. |
Beta Was this translation helpful? Give feedback.
-
|
In this application we are currently not using Caffeine based Cache but as discussed before I am aware it do provide operations to get an approximation of the N best (or worst) keys that I can get hold of by accessing the backing map so that is another option but this requires a bit more work as we need to see that it works at least as good for our access pattern... |
Beta Was this translation helpful? Give feedback.
-
|
I eventually amaged to solve this but it did require using a deprecated API merhod to get the backingmap. I tested it using Caffeinie as well where I by getting hold of the backingmap could use the policy.eviction.hottest(N) method. |
Beta Was this translation helpful? Give feedback.
-
|
The |
Beta Was this translation helpful? Give feedback.
-
|
Good to hear - have used it in a few occations and worried it would be
dropped one day :-)
…On Sat, Sep 6, 2025 at 1:45 PM Jonathan Knight ***@***.***> wrote:
The getBackingMap() method is not really deprecated, it is used by
internal code in Coherence. The reason it was marked as deprecated was to
discourage it use as directly accessing the backing map can be dangerous if
you are not careful, especially if you then modify any entries in it as it
could bypass some of Coherence locks and guarantees.
—
Reply to this email directly, view it on GitHub
<#146 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADXQF43FMKSI4G6LZVRPQT3RLCNJAVCNFSM6AAAAACFGKL7QKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZSGY3DINI>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
The |
Beta Was this translation helpful? Give feedback.
-
|
Sorry to hear that it is no longer actively developed by Oracle (did not know but
should have guessed when I recently saw Tim M was let go from Oracle)... I have
been a Coherence user in various ways from back the Tangosol days (even had some
meetings with Cameron and Gene many many years ago), then Oracle Enterprise version
and nowadays only CE for one MAJOR professional and some small personal hobby projects.
I must admit I saw the Oracle acquisition as a really bad thing (not an
Oracle fan in general due to the commercial side of things even though they
have created some really nice products) but they did keep Coherence alive a
number of years at least...
If most (or all) CE contributors have been payed Oracle staff nothing new
will happen with this project either from now then? In that case perhaps
time to start trying other alternatives that support "near like" cache
topologies (that is the key feature that has made me keep using Coherence
even though many people today prefers purely distributed caches like
Redis/Dragonfly, Memcached etc.). Infinispan seems kind of interesting when
reading about it but no idea how solid it is in production (something Coherence
have really been for me at least)...
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, the contributors to this project were basically the Coherence Engineering team. Unless any of the 14 of them no longer at Oracle continue to contribute then nothing much will happen. As the intention is for the remaining three members of the engineering team to continue to support Coherence with bug fixes then I expect this repo will still be updated with those same fixes. We are supposed to be releasing Coherence 15.1.1-0-0 in October, and there will be a corresponding CE 15.1.1-0-0 which is probably going to be the last CE release. This will then have any bug fixes ported to it too. There is already a 15.1.1-0-0 branch in this repo. |
Beta Was this translation helpful? Give feedback.
-
|
It was a pity graceful shutdown of a storage enabled node (orderly moving
all primally and backup partitions to other noded) that I wrote an
improvement proposal for never got implemented - it was the only thing I
was really missing to make Coherence work well in a cloud environment
(allowing scale in without elevated risk of data loss)...
…On Sun, Sep 7, 2025, 15:57 Jonathan Knight ***@***.***> wrote:
Yes, the contributors to this project were basically the Coherence
Engineering team. Unless any of the 14 of them no longer at Oracle continue
to contribute then nothing much will happen. As the intention is for the
remaining three members of the engineering team to continue to support
Coherence with bug fixes then I expect this repo will still be updated with
those same fixes. We are supposed to be releasing Coherence 15.1.1-0-0 in
October, and there will be a corresponding CE 15.1.1-0-0 which is probably
going to be the last CE release. This will then have any bug fixes ported
to it too. There is already a 15.1.1-0-0 branch in this repo.
—
Reply to this email directly, view it on GitHub
<#146 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADXQFZAZ35OUXH52IA7AVD3RQ2UNAVCNFSM6AAAAACFGKL7QKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZTGE4DSNQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As Coherence can perform eviction based on usage frequency and most recently accessed this information must ad I understand it be stored somewhere... is this information today readable in some way through an API (when I asked a similar question some years ago I interpreted the answer as no such info was available and never perused it further at that time).
Now the need has surfaced again. Even if I get the backing map (something I have used for some other custom stuff) I have not seen a way to get these statistics :-(
I think it would be valuable to be able to get this information without yourself having to duplicate it in the application...
Beta Was this translation helpful? Give feedback.
All reactions