View Complete Thread
  • Re: Unlock your iis7-aspnet performance

    Feb 19, 2011 10:11 PM|foxontherock|LINK

    Oh wow... so, as I can see in chapter 6, we're not using a "dirty workaround", we're using the "best practice we can do in our case" because our application is not alone on the server. We have several applications, that may be why we had trouble. Even SQL Server activity was locking our asp.net processes. And the article clearly say that if we have several hosted isolated processes, we should disable the gc server.

    That helps us and I hope it may help other people make their dirty code work fine. I understand that people writing perfect code will never need to use that dirty workaround.

    For those who need this, I'm happy to share it with you.

    That's all for this thread.