Kentico CMS Performance Report 6.0
This Kentico CMS Performance Report 6.0 was conducted by Kentico Software with intention to provide customers with information on what performance they can expect from Kentico CMS. Kentico CMS Software put in the best effort to conduct an unbiased test. Still, the performance of the website depends on many parameters, such as computer hardware, network configuration, client configuration, operating system and software configuration, site content, number of items in Kentico CMS database, information architecture, custom code and other factors. Kentico Software doesn't provide any guarantee that the same values will be achieved with otherthan tested configurations. The reader of this report uses all information in this report at his/her own risk. Kentico Software shall in no case be liable for any loss resulting from the use of this report.
Kentico CMS for ASP.NET provides excellent performance and scalability. Being built on the Microsoft ASP.NET platform, it leverages all its power. The tests were performed internally by Kentico staff on very common hardware (IntelCore2Quad at 2.66 GHz, 10k SATA II disks, 4 GB memory). Kentico has not used any high performance servers, so the results may be even better on more powerful hardware.
Basic Performance and the Impact of Caching
The slowest parts of a web application are typically accessing the database and rendering the content for a web browser. Kentico CMS optimizes the performance by storing content that is often accessed in a server memory. This mechanism is called caching. When another visitor comes to the same page, the page is already stored in the very fast computer memory and Kentico CMS can quickly send it to the browser without repeatedly accessingthe database and rendering the page. The following graph shows a comparison of how caching influences the performance of Kentico CMS (the test was conducted on a single machine with both web server and database). Caching can be configured for a particular part of the page this is calledcontent caching You can also configure Output caching that stores the whole page pre rendered in the memory. The following figure shows the impact of caching on the overall performance. The values represent the number of requests per second (RPS) which means how many pages can be viewed by the visitors per second.