OpenSTAs Results Graphs
Below is a list of the graphs available in OpenSTA, an expanded description of the meaning, and any hints on its intended use.
-
HTTP Monitored Bytes/Sec v Elapsed Time - Amount of HTTP throughput (just on the VUs selected to be monitored) throughout the run of the test.
-
HTTP Response Time v Number Of Responses - The time to get a response from a HTTP request while a number of responses was being received throughout the test run.
-
HTTP Errors / HTTP Requests - Number of HTTP requests returning with error codes while a given number of HTTP requests was being made throughout the test run.
-
HTTP Errors / Elapsed Time - Number of HTTP requests returning with error codes throughout the test run.
-
HTTP Responses / Elapsed Time - Number of replies to HTTP request received (per second) taken throughout the test run.
-
HTTP Response Time / Elapsed Time - The time to get a response from a HTTP request throughout the test run.
-
HTTP Active Users / Elapsed Time - The number of active VUs taken throughout the test run. This graph shows how well any ramp up and down works and can provide data points of the time given numbers of users were active.
The Timer Value graphs usually make most sense when only one Timer, or type of Timer, is selected.
-
Timer Values / Active Users - Averages of the Timer values taken for each period where a given number of users were active. This graph works best if the number of VU's if ramped up and down slowly. It is next to useless if you only have 1 VU or start all your VU's simultaneously.
-
Timer Values / Elapsed Time - Averages of the Timer values taken throughout the test run. This graphs works best if you are introducing certain types of performance effecting activity during different periods of the test run.
The various results listed as throughout the test run are probably the either a actual number of occurences (eg. HTTP Responses) or an average of the values returned (eg. HTTP Response Time) in 1 second time intervals throughout the test, although this needs to be confirmed.
ToDo: verify descriptions and add any user comments about graphs and there intended use.
FrequentlyAskedQuestions
