[ 
https://issues.apache.org/jira/browse/IGNITE-28919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikita Amelchev updated IGNITE-28919:
-------------------------------------
    Description: 
Replace the legacy communication IO test with management API commands. Preserve 
communication latency testing with clearer millisecond-based output, and add a 
new test for measuring message traversal through the {{TcpDiscoverySpi}} ring, 
including per-hop and total timings.

h3. Communication SPI

{code}
$ control.sh --io-test communication --node-id 
8f3c1d72-6a94-4b57-9e21-3d8f0a6c42b5

Communication SPI test
Source: srv-1 [id=8f3c1d72-6a94-4b57-9e21-3d8f0a6c42b5]
Parameters: warmup=5000 ms | duration=30000 ms | threads=1 | payload=0 bytes
Handling: system pool
RTT:
Target    Samples    Min, ms    Avg, ms    Max, ms
srv-2       142851      0.028      0.087      4.106
srv-3       142850      0.029      0.089      3.884
Estimated one-way delivery*:
Target    Direction    Min, ms    Avg, ms    Max, ms
srv-2     Request            0      0.045          4
srv-2     Response           0      0.042          3
srv-3     Request            0      0.046          3
srv-3     Response           0      0.043          3
* One-way delivery uses OS wall-clock time and requires synchronized node 
clocks.
  RTT uses a monotonic clock. System-pool handling includes executor dispatch 
time.
{code}

h3. Discovery SPI

{code}
$ control.sh --io-test discovery

TcpDiscoverySpi ring test
Coordinator: srv-1 [id=8f3c1d72-6a94-4b57-9e21-3d8f0a6c42b5]
Parameters: samples=10 | interval=100 ms | payload=100 bytes
Full-ring latency:
Samples    Min, ms    Avg, ms    Max, ms
     10      0.559      0.619      0.729
Estimated per-hop delivery (ring order)*:
>From     To       Min, ms    Avg, ms    Max, ms
srv-1    srv-2          0      0.000          0
srv-2    srv-3          0      0.000          0
srv-3    srv-1          0      0.000          0
* Per-hop delivery uses OS wall-clock time and requires synchronized node 
clocks.
  Full-ring latency uses a monotonic clock.
{code}

  was:Replace the legacy communication IO test with management API commands. 
Preserve communication latency testing with clearer millisecond-based output, 
and add a new test for measuring message traversal through the 
{{TcpDiscoverySpi}} ring, including per-hop and total timings.


> Add communication and discovery network test commands
> -----------------------------------------------------
>
>                 Key: IGNITE-28919
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28919
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Nikita Amelchev
>            Assignee: Nikita Amelchev
>            Priority: Major
>              Labels: ise
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Replace the legacy communication IO test with management API commands. 
> Preserve communication latency testing with clearer millisecond-based output, 
> and add a new test for measuring message traversal through the 
> {{TcpDiscoverySpi}} ring, including per-hop and total timings.
> h3. Communication SPI
> {code}
> $ control.sh --io-test communication --node-id 
> 8f3c1d72-6a94-4b57-9e21-3d8f0a6c42b5
> Communication SPI test
> Source: srv-1 [id=8f3c1d72-6a94-4b57-9e21-3d8f0a6c42b5]
> Parameters: warmup=5000 ms | duration=30000 ms | threads=1 | payload=0 bytes
> Handling: system pool
> RTT:
> Target    Samples    Min, ms    Avg, ms    Max, ms
> srv-2       142851      0.028      0.087      4.106
> srv-3       142850      0.029      0.089      3.884
> Estimated one-way delivery*:
> Target    Direction    Min, ms    Avg, ms    Max, ms
> srv-2     Request            0      0.045          4
> srv-2     Response           0      0.042          3
> srv-3     Request            0      0.046          3
> srv-3     Response           0      0.043          3
> * One-way delivery uses OS wall-clock time and requires synchronized node 
> clocks.
>   RTT uses a monotonic clock. System-pool handling includes executor dispatch 
> time.
> {code}
> h3. Discovery SPI
> {code}
> $ control.sh --io-test discovery
> TcpDiscoverySpi ring test
> Coordinator: srv-1 [id=8f3c1d72-6a94-4b57-9e21-3d8f0a6c42b5]
> Parameters: samples=10 | interval=100 ms | payload=100 bytes
> Full-ring latency:
> Samples    Min, ms    Avg, ms    Max, ms
>      10      0.559      0.619      0.729
> Estimated per-hop delivery (ring order)*:
> From     To       Min, ms    Avg, ms    Max, ms
> srv-1    srv-2          0      0.000          0
> srv-2    srv-3          0      0.000          0
> srv-3    srv-1          0      0.000          0
> * Per-hop delivery uses OS wall-clock time and requires synchronized node 
> clocks.
>   Full-ring latency uses a monotonic clock.
> {code}



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

Reply via email to