ASP. NET: problems caused by PAGE buffer settings

A few days ago, when the program uses Respoonse. Redirect ("a. aspx? F = 9 #12 "), I found that in IE, the page after the jump ignores the content after #. The strange thing is that when the same page is Redirect to itself, this problem won't exist, and it's hard to solve it. If you are ill about the problem, try again. Someone says setting the page Buffer to false may solve this problem, therefore, the buffer on page a is set to false. After verification, this is irrelevant to the above problem. However, due to negligence, I forgot to modify the buffer. The project was released yesterday, on the server, the execution time of the FA Xiang a page is astonishing. The page content is slightly larger, and the page usually times out. The execution time of the B page that implements the same function is basically 0-16, the database query times on page a are 3 and page B is 7, which is even more confusing. After a local test, page B is basically no different from the server, page a is between 90-300ms, while the obvious page B requires more data and queries than page a. The two are basically the same in terms of the page structure, because the two use the same UserControl, only the intermediate part of the expression is slightly different, Why is the gap between people under the same roof so big? I was puzzled when I deleted page elements one by one and found that page B had no essential effect. Page B was surprisingly fast. Page a was as slow as a stroke, so I went to Asia for help, basically speaking, I changed a to another one. When it was difficult to say that the buffer on page a was set to false, and B was suddenly set to true. Suddenly, it was a problem, correct it now. good! Page a is coming soon.

An accident caused such trouble, but summed up the rule that when the buffer is set to false, the page processing time is basically 10-20 times different from the setting of true, if the page with the same function is found in the future, the speed may vary a lot. If data processing and other factors are excluded, check whether the above problem exists.