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();
A Software Architect on the Sitefinity team, Martin Gebov has been with Progress for 10 years. Over the last couple of them, his main focus has been delivering the .NET Core solution. Prior to that, Martin helped build the new UI, as well as worked on multi-lingual support, the compiler, and other key components of the platform.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites