[Mono-bugs] [Bug 648900] New: High memory usage with sgen when serving through fastcgi-mono-server4

[bugzilla_noreply at novell.com]

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

https://bugzilla.novell.com/show_bug.cgi?id=648900#c0


           Summary: High memory usage with sgen when serving through
                    fastcgi-mono-server4
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.8.x
          Platform: x86-64
        OS/Version: Ubuntu
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GC
        AssignedTo: lupus at novell.com
        ReportedBy: michael at michael.ie
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41 Safari/534.7

When using Mono 2.8 tarball && XSP 2.8 tarball to serve ASP.NET MVC 2 pages
with fastcgi-mono-server(2|4) memory usage for mono keeps increasing.

Doing 120,000 page serves (from apachebench) with a simple webapp resulted in
 PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
3549 username  20   0  719m 673m  11m S  0.0 68.7  43:26.50 mono-sgen

As memory usage goes up, performance of the webapp goes down.

I repeated the tests today with the default skeleton ASP.NET MVC 2 site that
Visual Studio .net 2010 generates and exported MONO_GC_DEBUG=heap-dump just in
case the dump was useful. (It's 19GB)

Reproducible: Always

Steps to Reproduce:
export MONO_TRACE=E:all
export MONO_GC_DEBUG=heap-dump=/tmp/test-heap
mono --gc=sgen /opt/mono-2.8/lib/mono/4.0/fastcgi-mono-server4.exe
/applications=localhost:/:/var/www/asp/SimpleMVC2 /socket=tcp:127.0.0.1:9000
ab -n 60000 -c 15 -k http://localhost/Home/
top
Actual Results:  
719m virt 673m res

Expected Results:  
Expected a lot less mem usage

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