[
https://issues.apache.org/jira/browse/IGNITE-17345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713434#comment-17713434
]
Ignite TC Bot commented on IGNITE-17345:
----------------------------------------
{panel:title=Branch: [pull/10649/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10649/head] Base: [master] : New Tests
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Thin Client: Java{color} [[tests
5|https://ci2.ignite.apache.org/viewLog.html?buildId=7142822]]
* {color:#013220}ClientTestSuite:
AffinityMetricsTest.testCacheKeyAffinityMetricsReplicated - PASSED{color}
* {color:#013220}ClientTestSuite:
AffinityMetricsTest.testCacheKeyAffinityMetricsTx - PASSED{color}
* {color:#013220}ClientTestSuite:
AffinityMetricsTest.testCacheKeyAffinityMetricsPartitioned - PASSED{color}
* {color:#013220}ClientTestSuite:
AffinityMetricsTest.testQueryAffinityMetricsReplicated - PASSED{color}
* {color:#013220}ClientTestSuite:
AffinityMetricsTest.testQueryAffinityMetricsPartitioned - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7137296&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: Aleksey Plekhanov
> Priority: Major
> Labels: IEP-35, ise
> Fix For: 2.15
>
> Time Spent: 5h 20m
> 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)
