The following tables provide some examples of how big raw measure data files can become when you execute
load
tests with the shown settings.
Note: The size values are approximate values.
| Measurements
|
Duration of
load
test
|
Virtual users
|
Size of raw measure data file
|
| 1 measurement per second
|
1 hour
|
100
|
10 MB
|
| 3 measurements per second
|
5 hours
|
100
|
150 MB
|
| 1 measurement every 10 seconds
|
3 hours
|
100
|
3 MB
|
| Load
Test
|
Duration of
load
test
|
Virtual users
|
Size of all raw measure data files
|
Agents
|
Result packaging and download time*
|
| 10 pages (with 5 measurements per page), 1 page per second
|
1 hour
|
100
|
175 MB
|
2
|
30s
|
| 20 pages (with 5 measurements per page), 1 page every 3 seconds
|
5 hours
|
100
|
290 MB
|
2
|
45s
|
| 20 pages (with 5 measurements per page), 1 page every 3 seconds
|
10 hours
|
400
|
2,25 GB
|
4
|
3m 50s
|
| 20 pages (with 5 measurements per page), 1 page every 3 seconds
|
10 hours
|
4000
|
23 GB
|
40
|
7m 30s
|
* To gather these download times,
Silk Performer CloudBurst agents and a 100 Mbps internet connection to the
Silk Performer controller were used. The times include data processing and compression on the agents and the transfer to the controller.
Note: If you use cloud agents for your
load
tests, transferring large raw measure data files from the cloud agents to the controller can take a considerable amount of
time.
Note: For most
load
test scenarios it is sufficient to generate raw measure data for only a selected set of measures. To do so, use the BDL function
MeasureCollectRawData.