You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Chugunov (JIRA)" <ji...@apache.org> on 2017/07/17 11:18:00 UTC
[jira] [Updated] (IGNITE-5765) CacheMetrics interface cleanup,
documentation and fixes
[ https://issues.apache.org/jira/browse/IGNITE-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Chugunov updated IGNITE-5765:
------------------------------------
Description:
After moving to PageMemory offheap architecture some of metrics on CacheMetrics interface became vague.
The reason for this is that in Ignite2.0 data is always stored offheap but it is possible to configure additional on-heap area where frequently requested data is stored in deserialized form.
We need to revise the following metrics one by one and make a decision on each of them. All of them must be properly documented (right now documentation is rudimentary and doesn't allow to understand what to expect from each of them), some may be deprecated (and removed in later major release) and some must be reimplemented:
* getOffHeapGets (and how it relates to getCacheGets in case of near caches enabled);
* getOffHeapPuts;
* getOffHeapRemovals;
* getOffHeapEvictions;
* getOffHeapHits;
* getOffHeapHitPercentage;
* getOffHeapMisses;
* getOffHeapMissPercentage;
* getOffHeapEntriesCount (and how it relates to getHeapEntriesCount).
Any changes in API and fixes must also be implemented in platforms as well.
was:
After moving to PageMemory offheap architecture some of metrics on CacheMetrics interface became vague.
The reason for this is that in Ignite2.0 data is always stored offheap but it is possible to configure additional on-heap area where frequently requested data is stored in deserialized form.
We need to revise the following metrics one by one and make a decision on each of them. All of them must be properly documented (right now documentation is rudimentary and doesn't allow to understand what to expect from each of them), some may be deprecated (and removed in later major release) and some must be reimplemented:
* getOffHeapGets (and how it relates to getCacheGets in case of near caches enabled);
* getOffHeapPuts;
* getOffHeapRemovals;
* getOffHeapEvictions;
* getOffHeapHits;
* getOffHeapHitPercentage;
* getOffHeapMisses;
* getOffHeapMissPercentage;
* getOffHeapEntriesCount (and how it relates to getHeapEntriesCount).
> CacheMetrics interface cleanup, documentation and fixes
> -------------------------------------------------------
>
> Key: IGNITE-5765
> URL: https://issues.apache.org/jira/browse/IGNITE-5765
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Chugunov
>
> After moving to PageMemory offheap architecture some of metrics on CacheMetrics interface became vague.
> The reason for this is that in Ignite2.0 data is always stored offheap but it is possible to configure additional on-heap area where frequently requested data is stored in deserialized form.
> We need to revise the following metrics one by one and make a decision on each of them. All of them must be properly documented (right now documentation is rudimentary and doesn't allow to understand what to expect from each of them), some may be deprecated (and removed in later major release) and some must be reimplemented:
> * getOffHeapGets (and how it relates to getCacheGets in case of near caches enabled);
> * getOffHeapPuts;
> * getOffHeapRemovals;
> * getOffHeapEvictions;
> * getOffHeapHits;
> * getOffHeapHitPercentage;
> * getOffHeapMisses;
> * getOffHeapMissPercentage;
> * getOffHeapEntriesCount (and how it relates to getHeapEntriesCount).
> Any changes in API and fixes must also be implemented in platforms as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)