For running experiments we need a mechanism of generating load to mimic some operating profile. In the experiments Secretless is used as the proxy, however a custom client and server combination are used to allow traffic control during experiments. During experiments it is required to control the number of open connections, the number of connecting transmitting, how much data each connection is transmitting etc.
The requirements are specific to Secretless, and we have been unable to find off the shelf solutions for generating load. It is for this reason that we must write our own load generation code that creates connection using the custom client. The custom client has already been implemented on the telemetry branch.
NOTE that at this stage the traffic profile of interest is the light operating profile, defined as:
2000 open connections
10 active (transmitting) connection
50 waiting (non-transmitting) connections
Acceptance criteria
[ ] There is a load generation library for benchmarking experiments
[ ] The load generation library allows configuration generation of load against some input Secretless address. The configuration options supported are
[ ] Number of idle open connections
[ ] Number of transmitting open connections as a function of time
[ ] Amount of data transmitted on every request as a function of time
For running experiments we need a mechanism of generating load to mimic some operating profile. In the experiments Secretless is used as the proxy, however a custom client and server combination are used to allow traffic control during experiments. During experiments it is required to control the number of open connections, the number of connecting transmitting, how much data each connection is transmitting etc.
The requirements are specific to Secretless, and we have been unable to find off the shelf solutions for generating load. It is for this reason that we must write our own load generation code that creates connection using the custom client. The custom client has already been implemented on the telemetry branch.
NOTE that at this stage the traffic profile of interest is the light operating profile, defined as:
Acceptance criteria