netconf-clustering-scale.txt Report

Summary Information

Status:	All tests passed
Documentation:	netconf-restperfclient update performance test suite (clustered setup). Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html Perform given count of update operations on device data mounted onto a netconf connector (using the netconf-testtool-restperfclient tool) and see how much time it took. More exactly, it sends the data to a restconf mountpoint of the netconf connector belonging to the device, which turns out to turn the first request sent to a "create" request and the remaining requests to "update" requests (due to how the testtool device behavior is implemented). The difference from the "single node" test suite (see ../scale/performance.robot) is that the device is configured and the data on it created using one node in the cluster and the update operations are issued on a different node. This forces the cluster nodes to communicate with each other about the data to be sent to the device.
Start Time:	20250309 23:48:42.577
End Time:	20250309 23:52:25.822
Elapsed Time:	00:03:43.245
Log File:	log.html

Status:

Documentation:

netconf-restperfclient update performance test suite (clustered setup).

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform given count of update operations on device data mounted onto a netconf connector (using the netconf-testtool-restperfclient tool) and see how much time it took. More exactly, it sends the data to a restconf mountpoint of the netconf connector belonging to the device, which turns out to turn the first request sent to a "create" request and the remaining requests to "update" requests (due to how the testtool device behavior is implemented).

The difference from the "single node" test suite (see ../scale/performance.robot) is that the device is configured and the data on it created using one node in the cluster and the update operations are issued on a different node. This forces the cluster nodes to communicate with each other about the data to be sent to the device.

Start Time:

20250309 23:48:42.577

End Time:

20250309 23:52:25.822

Elapsed Time:

00:03:43.245

Log File:

log.html

Test Statistics

Total Statistics	Total	Pass	Fail	Skip	Elapsed	Pass / Fail / Skip
All Tests	8	8	0	0	00:03:35

Statistics by Tag	Total	Pass	Elapsed
1node	8	8	00:03:35
critical	8	8	00:03:35
netconf	8	8	00:03:35

Statistics by Suite	Total	Pass	Fail	Skip	Elapsed	Pass / Fail / Skip
netconf-clustering-scale.txt	8	8	0	0	00:03:43

Suite:

Test:

Include:

Exclude:

Help

Search fields

Tests can be searched based on suite and test names as well as based on tags. If multiple search criteria are used, only tests matching all of them are included. Search fields have same semantics as ‑‑suite, ‑‑test, ‑‑include and ‑‑exclude command line options, respectively.

Field	Explanation	Examples
Suite	Tests in matching suites are included. The pattern can match either suite's name or its full name that contains also parent suite names.	My Suite Root.Parent.Sui*
Test	Matching tests are included. The pattern can match either test's name or its full name that contains also parent suite names.	Example Name Root.Pa*.T???
Include	Tests that contain matching tags are included.	smoke bug-*
Exclude	Tests that contain matching tags are not included.	slow feature-4?

Patterns

All searches support * and ? wildcards and are case, space and underscore insensitive. Tag related searches also support AND, OR and NOT (case-sensitive) combining operators. If operators are used together, their precedence, from highest to lowest, is AND, OR, NOT. See Simple patterns and Tag patterns sections in Robot Framework User Guide for more details.