mprove Performance or Reduce Memory Usage in the Mono Compiler.

[GoogleCodeExporter]

This is a follow up to the previous two entries that were a great success
in memory reduction.

This is a continuation of  Issue #4 and Issue #64

In the Mono C# compiler, performance is tightly bound to memory usage.  
The less memory we use, the faster the compiler is.

The goal of this task is to reduce the memory usage used by the Mono C#
compiler.   A previous high-school student helped accelerate the Mono C#
compiler and eventually went to work for Google for the summers.

But as time has passed, the compiler has become chubbier and it could use a
number of passes to reduce its memory usage again (the last time we looked
at performance on it, it was two years ago).

The goal would be to reduce the memory consumption by 10% on bootstrapping
itself or in compiling any of the Mono libraires (mscolibr, System).

This task should take anywhere between 5 and 10 days.

The fix should not break the compiler, so all the tests should continue to run.

For additional information, see:
http://code.google.com/p/google-highly-open-participation-mono/issues/detail?id=
4

For the record, one thing that is useful is to use HeapShot to profile
applications,
more docs can be found here:

http://www.mono-project.com/HeapShot

You might want to add a ReadLine() before the compiler finishes to give you
a chance
to snapshot memory usage.

Original issue reported on code.google.com by miguel.d...@gmail.com on 6 Jan 2008 at 8:22

[GoogleCodeExporter]

Original comment by sebastie...@gmail.com on 6 Jan 2008 at 8:29

• Changed state: Open
• Added labels: Code, Performance
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Notice that work was done already in entry #64, any new updates should be 
different.

Original comment by miguel.d...@gmail.com on 6 Jan 2008 at 10:26