[Mono-bugs] [Bug 354701] New: Add a way to disable FileSystemWatcher for ASP.NET apps

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=354701


           Summary: Add a way to disable FileSystemWatcher for ASP.NET apps
           Product: Mono: Class Libraries
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: informatique.internet at fiducial.fr
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Hi,

I'm running ASP.NET in a clustered environnement. The ASP.NET apps are on an
NFS share, because they are running on several nodes.
For instance i'm running RHEL4 which has an old kernel which don't support
inotify. On RHEL4 the only FileSystemWatcher that works is the managed one.

With more than 20 different mod-mono-server instance we had 40% system CPU
taken only to do "FileSystemWatching". 

With mono 1.2.4 it was only 20%, i think it comes from the new Timer-sheduler
thread implementation.
With mono 1.2.5 the managed FileSystemWatcher leaks memory.
With mono 1.2.6 the managed FileSystemWatcher leaks CPU!

And with NFS there's no working FileSystemWatcher. So this feature is unusable
(and bad) in some situation. 
The only way i've found to disable it was to comment the related lines in
System.Web.

I think the proper way to achieve it, would be to let the user choose by
settings an environment variable (MONO_ASPNET_DISABLEFSW)

what do you think about that?


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.