[jira] [Commented] (IGNITE-17345) [IEP-35] Metric to track PA enabled request on ThinClient

["Ignite TC Bot (Jira)" <ji...@apache.org>]

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

Ignite TC Bot commented on IGNITE-17345:
----------------------------------------

{panel:title=Branch: [pull/10507/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10507/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7025939&buildTypeId=IgniteTests24Java8_RunAll]

> [IEP-35] Metric to track PA enabled request on ThinClient
> ---------------------------------------------------------
>
>                 Key: IGNITE-17345
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17345
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Nikolay Izhikov
>            Assignee: Luchnikov Alexander
>            Priority: Major
>              Labels: IEP-35, ise
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The crucial point to understand ThinClient performance is to know - Partition Awareness enabled or not.
> For now, it's impossible to understand how many request goes to node that is primary for key.
> It seems useful metrics to analyze PA behavior - two counters to track amount of requests for each server node 
> - one counter for keys current node is primary.
> - another counter for keys which require extra network hop between server nodes to serve the request.
> For environment with optimal performance second counter should be close to zero.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)