Prior to Sitefinity 7.1 one could experience an N+1 problem when opening a page for edit or when requesting it on the front-end for the first time. This was due to unnecessary database calls when Sitefinity is trying to construct the ASP controls on the requested page. As of 7.1 this issue has been resolved. Every user can now benefit from this optimization. The mechanism underneath consists of caching calculated metadata about hierarchical persistent objects(ChildProperties) in their parent (ControlProperty). Below are the scenarios when this metadata information is calculated:
With this mechanism the system is slowly optimizing itself as editors make changes to the pages. However if you would like to manually optimize and force recalculation of all the metadata, you can launch a scheduled task to do this for you. This is convenient for large systems - an example scenario is when templates that are used by a large amount of pages are rarely changed and therefore the metadata is not calculated.
Following is a code that does does all the calculation:
var task = new FixControlPropertiesTask(); task.WorkMode = FixControlPropertiesTask.Mode.FlagsOnly; task.Id = Guid.NewGuid(); var manager = SchedulingManager.GetManager(); manager.AddTask(task); manager.SaveChanges();
var task =
task.WorkMode = FixControlPropertiesTask.Mode.FlagsOnly;
task.Id = Guid.NewGuid();
var manager = SchedulingManager.GetManager();
View all posts from Martin Gebov on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
Copyright © 2019 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, 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.