With version 7.0, Sitefinity CMS has reduced the CPU startup time by 25% compared to Sitefinity CMS 6.3 by moving the compilation of the inline editing’s Razor templates from runtime to build time.
For more information, see Upgrade.
RECOMMENDATION: To improve the overall experience, configure the application pool to recycle the process as less as possible and configure your application to start automatically after recycle. You can configure it to recycle every 24 hours, during the time when the site is least accessed. For more information about how to configure auto start, see http://www.techbubbles.com/aspnet/auto-start-web-applications-in-aspnet-40/.
This way, the user who makes the first request after the recycle, will not experience slow response, because of the initialization. You can set up the recycle periods in the advanced settings of the application pool in the IIS management console. You must also disable recycling for idle time.
RECOMMENDATION: You can create an external service, which periodically browses the site. This way it will force any not compiled page to compile.
NOTE: The response may vary for different browsers and some request conditions. This is why this step may still be executed even though the output has already been cached. For example, if the request is authenticated with credentials that allow inline editing, output cache will not take effect and this step will always be executed. When testing output cache, make sure you are logged out.
RECOMMENDATION: Set output cache expiration to much longer period. The default is 2 minutes.
When publishing modified pages, or performing synchronization, it is possible that you experience degrading performance during the process due to fragmented database space. This may result in slow inserts of new data in the database and slow read times during publishing.
To avoid fragmentation of the database indexes and to improve write performance and scalability of the Microsoft SQL Server, Sitefinity CMS uses sequential GUIDs for database records' IDs where applicable. For more information, see Site synchronization key.
In addition, you can rebuild the database’s clustered indexes on a regular basis to maintain the database,optimize its performance, and avoid fragmentation of the clustered indexes.
RECOMMENDATION: Enable the database maintenance option in Sitefinity CMS or manually rebuild database indexes. For more information, see Database configuration.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity