Performance Benchmarks
- Baseer Khan
Owned by Baseer Khan
Terminology
| Term | Descriptions |
|---|---|
| Transactions | Transactions is the number of server hits. For example, 25 simulated users each hit the server with 10 repetitions, a total of 250 transactions |
| Availability: | Percentage of successful completed transactions |
| Elapsed time: | Elapsed time is the duration of the entire siege test. This is measured from the time the user invokes siege until the last simulated user completes its transactions. Shown above, the test took 14.67 seconds to complete. |
| Data transferred: | Data transferred is the sum of data transferred to every siege simulated user. It includes the header information as well as content. |
| Response time: | Response time is the average time it took to respond to each simulated user’s requests. |
| Transaction rate: | Transaction rate is the average number of transactions the server was able to handle per second, in a nutshell: transactions divided by elapsed time. |
| Throughput: | Throughput is the average number of bytes transferred every second from the server to all the simulated users. |
| Concurrency: | Concurrency is average number of simultaneous connections, a number which rises as server performance decreases. |
| Successful transactions | Successful transactions is the number of times the server returned a code less then 400. Accordingly, redirects are considered successful transactions. |
| Failed transactions | Percentage of failed transactions (timeout, not accepted) |
| Longest transaction | Longest time taken for a transaction |
| Shortest transaction | Shortest time taken for a transaction |
| CPU Units | CPU Allocated in Units by Cisco 829 Router |
Amazon Web Servies
Before we describe in details different generated data types, let's look at the data storage options that are available as part of the TQL. Storage is specified when <Storage> command when creating NewFacetInstance of type SffTqlFacet as part of your deployment package.