LunarPages benchmark results
Go back to Page 1
Click here to visit LunarPages
Click here to visit LunarPages
Scores table:
See how I rate the benchmark results.
Description |
Scores |
| Tech support speed | 5 |
| Tech support efficiaency | 8 |
| Hosting plan features | 10 |
| Price range | 8 |
| Control panel | 10 |
Benchmark results |
Scores |
| eMail delivery speed | 10 |
| Light PHP speed | 10 |
| PHP speed | 17 |
| PHP stress speed | 10 |
| BIG PHP stress speed | 5 |
| MySQL speed | 18 |
| MySQL stress speed | 15 |
| Benchmark scores | 85 |
| Final scores | 126 |
PHP + MySQL |
Result |
| Time taken for tests | 232.94 seconds |
| Time per request | 2239 ms |
| Complete requests | 100 |
| Failed requests | 0 |
Comments: |
|
| (1 concurrent request repeated 100 times/the test is performed until 100 successfully completed requests have been made. To gather the total number of sent requests you need to collect the completed and the failed requests/) Pretty good result. 223.94 seconds fall in the category “FAST”! Pretty good. There wasn’t a failed request at all – it guarantees that the users won’t see error messages as a result of a server overload. LunarPages have very good fast servers, suitable for sites that use MySQL. |
|
PHP + MySQL stress |
Result |
| Time taken for tests | 48.54 seconds |
| Time per request | 1213 ms |
| Complete requests | 40 |
| Failed requests | 0 |
Comments: |
|
| (5 concurrent requests repeated 8 times/the test is performed until 40 successfully completed requests have been made. To gather the total number of sent requests you need to collect the completed and the failed requests/) 0% failed requests and only 48 seconds. Apparently they have extra resources. |
|
PHP only |
Result |
| Time taken for tests | 228.29 seconds |
| Time per request | 456 ms |
| Complete requests | 500 |
| Failed requests | 0 |
Comments: |
|
| (5 concurrent requests repeated 100 times/the test is performed until 500 successfully completed requests have been made. To gather the total number of sent requests you need to collect the completed and the failed requests/) 0% failed requests. |
|
PHP stress |
Result |
| Time taken for tests | 93.80 seconds |
| Time per request | 465 ms |
| Complete requests | 200 |
| Failed requests | 0 |
Comments: |
|
| (10 concurrent requests repeated 20 times/the test is performed until 200 successfully completed requests have been made. To gather the total number of sent requests you need to collect the completed and the failed requests/) 0% failed requests – the same result as with the MySQL stress test. Obviously they have enough available resources. |
|
BIG PHP stress |
Result |
| Time taken for tests | 97.57 seconds |
| Time per request | 487 ms |
| Complete requests | 200 |
| Failed requests | 40 |
Comments: |
|
| (20 concurrent requests repeated 10 times /the test is performed until 200 successfully completed requests have been made. To gather the total number of sent requests you need to collect the completed and the failed requests/) 16.6% failed requests. It’s definitely not bad. This test is a pretty heavy one and increases the server load with 5-6 times. |
|