[Mono-list] [Fwd: mod_mono 1.2.4 for suse 10.0 taking up CPU after use]
Robert Jordan
robertj at gmx.net
Fri Aug 24 09:12:10 EDT 2007
Michał Ziemski wrote:
> at (wrapper runtime-invoke) System.Object.runtime_invoke_void
> (object,intptr,intptr,intptr) <0xffffffff>
> at System.IO.DefaultWatcher.DoFiles
> (System.IO.DefaultWatcherData,string,bool) <0x00167>
> at System.IO.DefaultWatcher.DoFiles
> (System.IO.DefaultWatcherData,string,bool) <0x00167>
> at System.IO.DefaultWatcher.DoFiles
> (System.IO.DefaultWatcherData,string,bool) <0x00167>
> at System.IO.DefaultWatcher.DoFiles
> (System.IO.DefaultWatcherData,string,bool) <0x00167>
> at System.IO.DefaultWatcher.UpdateDataAndDispatch
> (System.IO.DefaultWatcherData,bool) <0x0012b>
> at System.IO.DefaultWatcher.Monitor () <0x00150>
> at (wrapper delegate-invoke) System.MulticastDelegate.invoke_void ()
> <0xffffffff>
> at (wrapper runtime-invoke) System.Object.runtime_invoke_void
> (object,intptr,intptr,intptr) <0xffffffff>
>
> Does that ring any bells?
On your system, mono seems to use the default file system watcher
(based on polling). As more files it has to process,
as slower it gets.
Check whether your server is running inotify or fam.
Robert
More information about the Mono-list
mailing list