Perf issue with PreRender

[bryanp10]

I added my own Trace message to the OnPreRender event, and now my trace
output is rather interesting:

aspx.page Begin PreRender 1.323881 0.000060
OnPreRender start at 9/13/2005 4:08:15 PM 1.357799 0.033917
OnPreRender end at 9/13/2005 4:08:15 PM 1.922175 0.564376
aspx.page End PreRender 2.640666 0.718491


Between my Trace call and the built-in ASP.NET trace functionality,
there is a span of almost three quarters of a second! The message
"OnPreRender end" is the LAST line of code in that method. What code
is running during the time between this trace call and ASP.NET's trace
output?!? It's obviously taking up a significant time slice.

 

[Bruce Barker]

asp.net is running OnPreRender for each control added to the page
collection. Most likely one of your controls is doing at lot of work in
prerender.

-- bruce (sqlwork.com)