| Company URL | http://www.activevps.dk |
| Demo store URL | http://magento.activevps.dk |
| Price per month | 27 EUR |
| Store contention ratio | |
| Bandwidth | 100,000MB |
| Disk Space | 2,000MB |
| Databases | |
| Minimum contract | 12 Months |
| Transaction Rate | 77.58 TPS | |
| Initial Page Load | 0.14 secs | |
| Throughput | 99.78 kB p/s | |
| The TPS figure above is calculated based on our real world benchmark of 10 concurrent users across 15 demo store pages. |
||
| You can read more about how we calculate these figures and how we rank performance overall on our "how we do it" section. |
||
The following graph measures the performance of the server with varying levels of concurrency. Values for full transactions per second (TPS), data downloaded, and network throughtput were measured with 1, 2, 5, 10, 20 and 30 concurrent users. This test was custom made to reflect a real-world simulated load. Supplied with 15 different urls (mixed category/index/search requests), the script downloads the HTML and all other documents inline, including CSS, JavaScript and Images (like a normal user would). This is the best possible test to fairly compare hosts as it truly shows how it can handle a multitude of simultaneous connections.
The purple line shows the data downloaded during the tests (for a single user average). If this line dips at any point, it shows a transaction failure.
The following graph measures the performance of the server with varying levels of concurrency. Values for full transactions per second (TPS), data downloaded, and network throughtput were measured with 1, 2, 5, 10, 20 and 30 concurrent users. The test is based loosely on the operation of mainstream benchmark tools like Apache Bench (ab) and Siege. The test runs by downloading only the HTML content from a selection of 50 urls. This places the load on the PHP engine and highlights any performance shortcomings.
The purple line shows the data downloaded during the tests (for a single user average). If this line dips at any point, it shows a transaction failure.
The following graphs measure the performance of the server with varying levels of concurrency. Values for full transactions per second (TPS), data downloaded, and network throughtput were measured with 1, 2, 5, 10, 20 and 30 concurrent users.
Only the top 10 best (or worst as applicable) results are shown in each graph.
Sorted from best performing (green), to least best perfoming (red)
Sorted from best performing (green), to least best perfoming (red)
When trying to understand the failure rate - the position of the line is not important. The important factor is if the line is completely horizontal. Any dips or bends in the line indicates a failure.
When trying to understand the failure rate - the position of the line is not important. The important factor is if the line is completely horizontal. Any dips or bends in the line indicates a failure.
Sorted from best performing (green), to least best perfoming (red)
Sorted from best performing (green), to least best perfoming (red)
Sorted from best performing (green), to least best perfoming (red)
Sorted from best performing (green), to least best perfoming (red)