http://bugzilla.novell.com/show_bug.cgi?id=564236
http://bugzilla.novell.com/show_bug.cgi?id=564236#c3 Marek Habersack <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|mod_mono |Sys.Web Product|Mono: Tools |Mono: Class Libraries QAContact|[email protected] |[email protected] Severity|Major |Normal --- Comment #3 from Marek Habersack <[email protected]> 2009-12-14 09:23:38 CET --- The statistics you provide in comment #1 suggest your site serves slightly over one request per second, with limit of 100 requests you are probably queueing some amount of requests and, depending on what the applications do, it may result in a surge of memory usage when the requests are dequeued. Also, at some point the requests may be serialized (as you probably have 2-4 cores in your CPU, only that many requests can be served at the time for real) which might increase memory pressure when they are finally ran. The auto-hosting feature uses a single instance of mod-mono-server to service _all_ of the requests. I would suggest starting with either raising the active requests limit or removing it altogether for testing sake. Also, perhaps you should consider moving some of the sites away from autohosting? This issue will be very hard to reproduce and thus to debug unfortunately. Does it happen at exactly the same time every day? Do any cronjobs run at that time? If yes, what do they do? Can you pick up a pattern of what's happening every time memory usage grows so rapidly? I find it hard to believe System.Web, XSP or mod_mono suddenly have such hunger for memory. If you can, could you replicate your server and run some traffic simulation tests on it using 2.4.3 and 2.6rc (and perhaps trunk) to see if you can reproduce the issue somehow? As for the 2.4.2.2 problem - I will need you to turn debugging on in that server so that we can get line numbers in the stack trace. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
