Set the Trace attribute to false.
Setting the trace attribute will help, but it doesn't exactly answer
Simon, perhaps you need to have to test to see if caching the user is
worth the effort to begin with.
But an even broader question: how do you know you're not seeing any
improvement in performance?
<%=Now%> will always output the time, but I'm under the assumption
you're running it at the beginning of the page and at the end of the
Anyway, these guys may be a better help to you then me. Here's a solid
article on caching in ASP.NET:
On May 23, 12:50 pm, Alexey Smirnov <email@example.com> wrote:
Thanks for your replies.
After some Googling, it seems this issue is due to having a
response.flush in our code, which terminates the current requests
thread and flushes the output to the client.