We just announced our new expert How-To series, where we’ll be bringing you some of the best practices and techniques we’ve been using with customers.
The post this week is about the Response.Flush API, a silent but deadly performance killer. Many of our ASP.NET customers experience performance degradation and hangs because of it, so its one of the top things on our radar. The How-To talks about it in more detail and provides some strategies for addressing it.
Read it here: https://www.leansentry.com/HowTo/AspNet-Response-Flush-Poor-Performance.
Want to get all the best practices? Sign up for the How-To newsletter. This way you’ll get our weekly How-To posts and additional guides straight in your email.
The changes we made is below
After we made a change pages buffer=”false”
We got the error below:
System.Web.HttpException (0x80004005): Cannot redirect after HTTP headers have been sent.
at System.Web.HttpResponse.Redirect(String url, Boolean endResponse, Boolean permanent)
at Verizon.mOrdering.Helper.Common.Base.OrderingBase.NavigateToErrorPage(String errMessage, String IsFiosAppflow)
at Verizon.mOrdering.Helper.Common.Base.OrderingBase.Page_Error(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.TemplateControl.OnError(EventArgs e)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)