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

Paolo Molaro lupus at ximian.com
Tue Oct 31 06:58:07 EST 2006

On 10/29/06 Kornél Pál wrote:
> I'll probably be able to fix that one as well, but my very-very big problem 
> is that vbnc is so undarebly slow on Mono that it's quite impossible to wait 
> for the compiler to reach again the stage where it's failing.
> If the results of previous stages could be "serialized" it could save a lot 
> of time and the actual stage could be debugged.

This is not going to happen, because it involves a lot of work and
doesn't solve any problem. There are two issues here:
*) vbnc's implementation makes it very slow
*) vbnc running on mono hits some codepaths that makes it even slower
than it is already

> Any help on speeding up vbnc is welcome.

Someone should provide a current vbnc binary and any assemblies it
depends on so that it runs on the current svn version of mono.
Please do not include the ugly additional GC thread hack.
Also include a largish VB program that vbnc can compile
(in, say, 10-20 seconds on the MS runtime).
When that is available, we can profile it on Linux and see where it
spends all that time and why.


lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better

More information about the Mono-devel-list mailing list