Support for SecNetPerf Variables to be in Units of CPU Count

[nibanks]

Description

Added the ability for secnetperf to use the unit of cpu to indicate it's a multiple of the number of CPUs on the machine. This is usefull for generically defining a perf test case that scales with the type of machine its run on.

Examples:

> secnetperf.exe -target:localhost -conns:1cpu -rstream:1 -plat:1 -up:100 -down:100 -run:1s
Started!

Result: 124985 RPS, Latency,us 0th: 37, 50th: 164, 90th: 414, 99th: 500, 99.9th: 557, 99.99th: 6013, 99.999th: 13355, 99.9999th: 13396, Max: 13396
App Main returning status 0


> secnetperf.exe -target:localhost -conns:2cpu -rstream:1 -plat:1 -up:100 -down:100 -run:1s
Started!

Result: 277589 RPS, Latency,us 0th: 47, 50th: 108, 90th: 352, 99th: 803, 99.9th: 1187, 99.99th: 10995, 99.999th: 20259, 99.9999th: 21174, Max: 21174
App Main returning status 0

Testing

Locally

Documentation

None atm

[csujedihy]

2cpu = 2 connections per CPU?

[nibanks]

2cpu = 2 connections per CPU?

Essentially. 2 * CPU count connections

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.91%. Comparing base (eb76333) to head (c80907a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4588      +/-   ##
==========================================
- Coverage   87.04%   85.91%   -1.13%     
==========================================
  Files          56       56              
  Lines       17354    17354              
==========================================
- Hits        15106    14910     -196     
- Misses       2248     2444     +196     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.