title: Response.Redirect big news
body: <p>I got a strange phenomenon when using Response.Redirect in my asp.net app, here is the thing:</p>
  
  <pre><code>Response.Redirect("~/somepage.aspx");  
  </code></pre>
  
  <p>when the page is just in root of virtual dir, it will take almostly 15 milliseconds to get(find) the page</p>
  
  <pre><code>Response.Redirect("~/somedir/somepage.aspx"); 
  </code></pre>
  
  <p>when I move the page to a dir, it will take almostly 2 seconds to get(find) the page,  the time is unbearable for browsing website, and I tried lots of ways to fix it eventually still don't know why this happen, could you nice guys give me any addvices,  thanks a lot.
  btw, somepage.aspx have nothing in it, except for two words in body node: "help me".</p>
  
  <p>p.s. there are 72 aspx pages in somedir,  about 10 aspx pages in root dir.</p>
  
  <p>I found some clue, I create a new dir newdir with only somepage.aspx in it, then the time spent for getting the page is 15 milliseconds again, so the test leads me to the this conclusion: the time Response.Redirect works is based on the number of files in dir, mayber I 'm wrong about it, but that's the only fact I got.</p>