Umbraco 4.1 Benchmarks Part 1 (Do Over)
Doh! Turns out that my first Umbraco 4.1 benchmarks was done on a build of 4.1 that had a couple of bugs in it :( BUT, this turns out to be even better for 4.1 that I previously thought! (plus there’s bugs fixed now :) If you didn’t read the last post, i recommend that you do as it has some insight as to how these stats came to be.
So, without further adieu, here’s the (true) new results:
| Test | Stats | 4.0.3 | 4.0.3 client cached |
4.1 | 4.1 client cached |
|---|---|---|---|---|---|
| Content app | Completed Requests | 68 | 7 | 45 | 5 |
| Response (KB) | 687.05 | 72.48 | 382.42 | 11.61 | |
| Edit content home page |
Completed Requests | 50 | 2 | 34 | 1 |
| Response (KB) | 385.10 | 47.28 | 335.02 | 11.94 | |
| Expand all content nodes |
Completed Requests | 17 | 17 | 16 | 16 |
| Response (KB) | 18.47 | 18.47 | 13.96 | 7.54 | |
| TOTALS | Completed Requests | 135 | 26 | 95 | 22 |
| Response (KB) | 1063.62 | 138.23 | 731.40 | 31.09 |
So to recap, here’s the total average savings in 4.1
- Without client cache (First run)
- Number of completed requests: 30% Less
- Response bandwidth: 31% Less
- With client cache
- Number of completed requests: 6% Less
- Response bandwidth: 78% Less
Need an Umbraco Master?
Here at Simon Antony, we have an in house certified Umbraco Grand Master available for hire. Got a problem with your site, need architecture advice, give us a call to speak to Simon directly and see how we can help
Contact Simon Today!