[Mono-dev] VBNC uses too much CPU and RAM on Mono

Kornél Pál kornelpal at gmail.com
Tue Oct 31 15:01:49 EST 2006

>> Is that a problem if the compilation cannot complete? Currently vbnc is 
>> able
>> to finish the resolve phase on Mono when bootstrapping and fails in early
>> define phase.
>How much time does it take to complete the resolve phase? I thought that
>was the issue given this thread subject. If there are other issues, they
>should be discussed in another thread.
>And yes, it is a problem if it makes the compiler so slow to be unusable
>as you claim it is.

The resolve phase is part of compilation so the subject covers the problem.
When doing bootstrap (compiling vbnc using vbnc) finishing the resolve phase 
takes up to 2 minutes on MS.NET. Doing the same on Mono takes at least 1 
hour on the same machine.

So I think it's worth to profile the bootstrap altough it cannot finish 
further phases yet. If that's a problem simply abort compilation arfter 
resolve phase is finished.

>This is why I requested a sample program that can compile, instead of
>trying to profile a program that never finishes.
>When someone posts that we can start to profile, so far nobody did,
>I guess we have to wait for some vb programmers to show up.

I guess that vbnc is not able to finish compiling other huge programs just 
like itself. But I can't fix SRE to support vbnc because it takes at least 1 
hour to reach the point when it fails that makes debugging and probing 
patches quite impossible.

I think that you could profile the vbnc bootstrap until the end of resolve 
phase because it requires a lot of time and memory by itself.


More information about the Mono-devel-list mailing list