Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Near cache statistic #30

Closed
hazelcast opened this issue Mar 23, 2012 · 6 comments
Closed

Near cache statistic #30

hazelcast opened this issue Mar 23, 2012 · 6 comments
Assignees
Labels
Source: Internal PR or issue was opened by an employee Type: Enhancement
Milestone

Comments

@hazelcast
Copy link
Collaborator

Add possibility to retrieve statistic about near cache like
IMap.getLocalMapStats() does.
For example, EntryCount and EntryCost for objects in near cache.

Migrated from http://code.google.com/p/hazelcast/issues/detail?id=421

@cameronbraid
Copy link

I would like this feature too..

Is there a targeted version for which this feature will be implemented ?

@ghost ghost assigned eminn Oct 8, 2013
@lukasblu
Copy link
Contributor

Hej,

I'd like to have this feature too.

EntryCount should be straight forward to implement. EntryCost (memory consumption could be difficult for InMemoryFormat.OBJECT, but as with the map statistics, you could simply only support this for InMemoryFormat.BINARY).

Besides the two already mentioned stats, a measure of hit ratio would be awesome - e.g. number of hits and number of misses. For a cache this is really fundamental to decide if maintaining this cache is useful.

Thanks and best,
Lukas

@jerrinot
Copy link
Contributor

there are already hits & getCount in the LocalMapStats.
Isn't getCount - hits == misses?

@eminn
Copy link
Contributor

eminn commented Dec 24, 2013

I already did some work for that but never created pull request for it. I will finish that, then create a pull request for it. Hopefully version 3.2 will contain near cache statistics

@lukasblu
Copy link
Contributor

@jerrinot sure, however, this is on the map - and not on the near cache.

I'd like to know, for example, the ratio of get-requests which were served directly by the near cache versus the requests that had to go to the map, possible fetch the entry from a remote node, deserialize the entry and then return it.

This allows me to decide if a cache is useful. E.g. if most of the requests go to the map anyway, for example, because entries in the near cache are invalidate before I can benefit from having it in the near cache, then the cache can/should be removed.

Okay?

Best,
Lukas

@eminn
Copy link
Contributor

eminn commented Dec 27, 2013

see #1458

@eminn eminn closed this as completed Dec 27, 2013
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Jan 28, 2020
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
…ing-to-configuration

Allow multiple Hazelcast instances in the same namespace with different labels
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
…azelcast#30)

* fixes for hazelcast-aws Github issues hazelcast#29 and hazelcast#22

* fixes for checkstyle errors

* fixes for checkstyle errors

* extended strategy factory tests

* removed Configuration to AwsConfig

* Configuration fixes, we now allow w/out any creds, or iam-role defined in config file.

* missing default value for timeout added
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Type: Enhancement
Projects
None yet
Development

No branches or pull requests

5 participants