title: Should i use HttpResponse.End() for a fast webapp?
body: <p><a href="http://msdn.microsoft.com/en-us/library/system.web.httpresponse.end.aspx" rel="nofollow noreferrer">HttpResponse.End()</a> seems to throw an exception according to msdn. Right now i have the choice of returning a value to say end thread (it only goes 2 functions deep) or i can call end().</p>
  
  <p>I know that <a href="https://stackoverflow.com/questions/1771216/is-there-really-a-performance-hit-when-catching-exceptions/1771544#1771544">throwing exceptions is significantly slower</a> (read the comment for a C#/.NET test) so if i want a fast webapp should i consider not calling it when it is trivially easy to not call it?</p>
  
  <p>-edit- I do have a function call in certain functions and in the constructor in classes to ensure the user is logged in. So i call HttpResponse.End() in enough places although hopefully in regular site usage it doesn't occur too often.</p>