|Content app||Completed Requests||68||7||46||6|
|Edit content |
|Expand all |
Note: the above is based on <compilation debug=”false”> being set in the web.config. If it is set to true, the compression, combination and minification for both the ClientDependency framework and ScriptManager is not enabled. Also, this is not based on having IIS 7’s dynamic/static compression turned on, these benchmarks are based on Umbraco performing ‘as is ‘ out of the box which will be the same for IIS 6.
Though there’s only 3 tests listed above, these results will be consistent throughout all applications in the Umbraco back office in version 4.1.
The 4.1 difference:
- In 4.0.3, all ScriptResource calls generated by ScriptManager were not being compressed or minified. This was due to a browser compatibility flag that was set in the base page (this was probably very old code from pre v3!).
- Script managers in the back-office have the ScriptMode=”release” explicitly set (for minification of ScriptResource.axd)
- Combination, compression, minification of dependencies
- Rogue script/style detection (for those scripts/styles that weren’t registered with the framework will still get compressed/minified)
- Compression/minification of specified Mime types, in this case all JSON requests in the back office (namely the tree)
Compared to 4.0.3, this is a HUGE difference with some serious performance benefits!