ASP.NET Performance issue: Large number of application restarts due to virus scanning

re: ASP.NET Performance issue: Large number of application restarts due to virus scanning

Mufasa — Wed, 14 May 2008 16:38:49 GMT

Couldn't you also just turn off Last Access updates in the NTFS settings accomplish the same thing? That is the only thing the virus scanner is changing on the file, correct? (And who needs Last Access anyway?)

re: ASP.NET Performance issue: Large number of application restarts due to virus scanning

Tess — Wed, 14 May 2008 16:41:19 GMT

Thanks Mufasa, I think you're absolutely correct

re: ASP.NET Performance issue: Large number of application restarts due to virus scanning

GlenH — Thu, 15 May 2008 04:33:14 GMT

Wow! I hope you realize that there are probably not 2 developers in a thousand that could do this level of debugging and analysis. Thanks for sharing your knowledge and techniques.

re: ASP.NET Performance issue: Large number of application restarts due to virus scanning

Nick — Wed, 21 May 2008 23:59:42 GMT

And this is one of many reasons why you shouldn't be running virus scanners on production boxes. Why wasn't the solution to uninstall the scanner?

Very interesting and great debugging regardless.

re: ASP.NET Performance issue: Large number of application restarts due to virus scanning

Tess — Thu, 22 May 2008 09:15:35 GMT

I am not sure that I would recommend anyone to not run a virus scanner on a production box, but there as Mufasa mentioned you can turn off Last Access updates, and work with the virus scanner vendor to find out what you need to do to avoid updating attributes on files in the web content directories and the temporary asp.net files.

5月20日链接篇： ASP.NET, ASP.NET AJAX, .NET, Visual Studio, Silverlight, WPF

Joycode@Ab110.com — Fri, 23 May 2008 01:18:46 GMT

【原文地址】 May 20th Links: ASP.NET, ASP.NET AJAX, .NET, Visual Studio, Silverlight, WPF 【原文发表日期】 Tuesday

Links op 20 mei: ASP.NET, ASP.NET AJAX, .NET, Visual Studio, Silverlight, WPF

Scott Guthrie's Blog in Dutch — Sat, 24 May 2008 10:33:59 GMT

Mijn verontschuldigingen voor de weinige posts de laatste weken. Mijn werk en leven zijn enorm de druk

The root cause for application performance problems might seem to be totally unrelated

Green Dragon's Lair — Sun, 25 May 2008 01:11:51 GMT

I just read a post on If broken it is, fix it you should , where he's debugging a performance problem

Liens du 20 mai: ASP.NET, ASP.NET AJAX, .NET, Visual Studio, Silverlight, WPF

Scott Guthrie's Blog in French — Tue, 03 Jun 2008 07:39:59 GMT

Mes excuses pour le peu de publications au cours des dernières semaines – le travail et la vie en générale

re: ASP.NET Performance issue: Large number of application restarts due to virus scanning

Eyal — Mon, 28 Jul 2008 15:02:26 GMT

Can you explain the difference between FCNMode=0 and FCNMode=2 in terms of functionality? We have hit the following problem: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/-1/threadid/182071/scope/posts/Default.aspx

and it seems like setting it to 2 solves it. But we are not quite sure what's the difference between them.

re: ASP.NET Performance issue: Large number of application restarts due to virus scanning

Tess — Mon, 04 Aug 2008 23:04:21 GMT

The difference between 0 and 2 is just how many objects are monitoring file change notifications. i.e. one per sub directory (0) or one object monitoring all directories (2)

Without knowing the exact details I am assuming that the reason 2 solves the problem is probably because something in the setup you have causes the objects to lock up if you have multiple objects working as they would probably have to synchronize then...