Version 7 of the Sitecore ASP.NET web Content Management System (CMS) provides pipeline profiling, which lets you monitor utilization, performance, and other aspects of Sitecore pipelines. You can use pipeline profiling to identify opportunities to improve system performance by optimizing pipelines. Before you read this blog post, please read the Sitecore 7: Introduction linked in the Resources section at the end of this page.
Pipelines separate the implementation of processes into a series of discrete processors, each typically responsible for a single operation invoked by one or more components somewhere within the system.
Sitecore 7 disables pipeline profiling by default. To enable pipeline profiling, rename the /App_Config/Include/Sitecore.PipelineProfiling.config.disabled Web.config include file to Sitecore.PipelineProfiling.config, or otherwise set the Pipelines.Profiling.Enabled setting in the Web.config file to true. Optionally, set the value of the Pipelines.Profiling.MeasureCpuTime setting to true, which adds some overhead but provides additional pipeline profiling detail.
To access pipeline profiling information, go to the /sitecore/admin/pipelines.aspx page, which requires that you log in as a Sitecore administrator. The grid displays rows for each processor in each pipeline, starting with a summary row for the pipeline.
The Refresh button reloads the page to render updated information. The Reset button resets pipeline profiling details, similar to resetting the application pool. This is also makes the legend more clear. You can use the text box below the buttons to filter the list of pipeline names.
The first column indicates the pipeline or processor with numbered icons in various colors that might help to identify the worst performers in each pipeline. Hover over the name of a processor to see defails for that component.
Additional columns indicate:
In some cases, a high value that could indicate opportunity for improvement may not be as important as something else that shows a smaller room for improvement. For example, performance in the initialize pipeline invoked once at application startup may not be as critical as performance in the httpRequestBegin pipeline invoked once for each HTTP request.
Very nice feature John! Any word on when the community technology preview will be made available? I'm anxious to explore the new bits.
Nothing I am allowed to say other than Sitecore 7 will soon go to general availability without a technical preview.
Very much looking forward to trying Sitecore 7! Looks great
Hi John, I have one particular requirement where in pipelines I have to read content or field values and if I try to read using the multi list selection, I am getting null values. I even tried for all other field values but I am getting nulls. Could you please help me? Looking forward to hear form you. Thanks in advance. Cheers Kapil Oliveti
The most likely issue is publishing. See: sdn.sitecore.net/.../ShowPost.aspx