Documentation/Display issue with rates

[ck-9000]

I'm running a test based on the raw latency test case and I noticed an issue with the docs and how the config is displayed in the UI.

Relevant part of the profile here:

add tests client tcp port 0 test-case-id 0 src 10.0.0.1 10.0.0.1 sport 10001 15000 dest 10.0.0.252 10.0.0.252 dport 6001 6100
set tests criteria   port 0 test-case-id 0 run-time 300
set tests rate       port 0 test-case-id 0 send 10
set tests rate       port 0 test-case-id 0 open 10
set tests rate       port 0 test-case-id 0 close 10
set tests client raw port 0 test-case-id 0 data-req-plen 16 data-resp-plen 16 rx-timestamp tx-timestamp
set tests async      port 0 test-case-id 0

These are obviously small numbers; just for illustration.

In the docs, the "Configure test profile rates" section, the data rate definition is word-for-word identical to the setup rate. The setup rate seems to be to what it refers.

When running the tests, the config view shows:
|Rate Open : 10s/s
|Rate Close : 10s/s
|Rate Send : 10s/s

So I don't know what s/s is, but with open and close it is obviously connections opened or closed per second. But with rate send, is it bytes? kbytes? The documentation doesn't help here.

[davvore33]

Hi @ck-9000 ,
we mean "session sends per second" from an application perspective, so not necessarily a single packet per send

[ck-9000]

Ah, thanks. What about the data rate thing? Isn’t that about bytes rather than sessions?

…

Sent from my iPhone On Nov 30, 2018, at 5:15 AM, Matteo Triggiani <[email protected]<mailto:[email protected]>> wrote: Hi @ck-9000<https://github.com/ck-9000> , we mean "session sends per second" from an application perspective, so not necessarily a single packet per send — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#90 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ArMj6cwyrcObYovyD3WuWuIPRMddPViDks5u0QUlgaJpZM4Y6iEA>.

[davvore33]

setup rate is the number of connections that the clients in the test are allowed to initiate [per second]
data rate is the number of connections that the clients in the test are allowed to send traffic [per second]

is this what you need to know?

[ck-9000]

Based on my testing it would appear to be an actual data rate, like in bytes per second because when I double that value, the switch interfaces show double the bandwidth regardless of how many connections or how fast they open. It seems to be a bandwidth cap. Like if I set it to 10,000, I get a bit over 10 megabit on the switch interfaces it is using, and if I set it to 100,000 I get a little over 100 megabit.

[davvore33]

when you set 100000 as send rate, per each data packet you have:

• client sends pkt: 14 bytes eth + 20 IP + 20 TCP + 16 (data)
• server sends reply
• client sends ack: 14 bytes eth + 20 IP + 20 TCP
  so from client to server for one client you have (54+16+54)1000008bits
  which is 99200000, so probably this is a bit confusing from an external point of view

is it clear now?

[ck-9000]

That jibes with what I'm seeing. Essentially it caps how many sessions are going at once, so total bandwidth becomes a function of the value of data-req-plen/resp-plen and that rate?

[davvore33]

@ck-9000 exactly