[ 
https://issues.apache.org/jira/browse/IGNITE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271935#comment-16271935
 ] 

Valentin Kulichenko commented on IGNITE-6846:
---------------------------------------------

As for the API, how about this?

{code}
public long getEntryProcessorInvocations();
public long getEntryProcessorReadOnlyInvocations();
public long getEntryProcessorHits();
public long getEntryProcessorMisses();
public long getEntryProcessorHitPercentage();
public long getEntryProcessorMissPercentage();
public long getEntryProcessorPuts();
public long getEntryProcessorRemovals();
public long getMinEntryProcessorInvocationTime();
public long getAverageEntryProcessorInvocationTime();
public long getMaxEntryProcessorInvocationTime();
public long getMinEntryProcessorReadOnlyInvocationTime();
public long getAverageEntryProcessorReadOnlyInvocationTime();
public long getMaxEntryProcessorReadOnlyInvocationTime();
{code}

> Add metrics for entry processor invocations
> -------------------------------------------
>
>                 Key: IGNITE-6846
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6846
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.3
>            Reporter: Valentin Kulichenko
>            Assignee: Alexey Kuznetsov
>            Priority: Critical
>              Labels: iep-6
>             Fix For: 2.4
>
>
> {{CacheMetrics}} object has multiple metrics for various cache operations 
> like {{get}}, {{put}} and {{remove}}, but nothing for 
> {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for 
> example:
> * Total number of `invoke` operations executed.
> * Number of `invoke` operations that included updates.
> * Number of read-only `invoke` operations.
> * Min/max/avg execution time.
> * ...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to