You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Luchnikov Alexander (Jira)" <ji...@apache.org> on 2023/04/13 08:00:00 UTC

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

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

Luchnikov Alexander commented on IGNITE-17345:
----------------------------------------------

Unable to complete the task, you can take it to work.

> [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
>            Priority: Major
>              Labels: IEP-35, ise
>             Fix For: 2.15
>
>          Time Spent: 4h
>  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)