Hello,
> The compiler is effectively keeing a linked list of all the tokens, and it
> keeps them until the compiler finishes (tokens are kept since they contain
> the source location for the token and would be necessary for any error
> messages.) I'm quite sure I can remove the entire list p
Hello,
>>> > > Any help on speeding up vbnc is welcome.
First I'd like to apoligize for leaving this unanswered for so many days,
the problem was that my motherboard went up in smoke and I had to get a
new computer :(
> It seems that the linked list for *all* files was kept for the *entire*
: "Miguel de Icaza" <[EMAIL PROTECTED]>
To: "Kornél Pál" <[EMAIL PROTECTED]>
Cc: "Paolo Molaro" <[EMAIL PROTECTED]>;
Sent: Wednesday, November 01, 2006 6:19 AM
Subject: Re: [Mono-dev] VBNC uses too much CPU and RAM on Mono
> Hello,
>
>
Hello,
> Sorry if I don't understand what you need but I have no experience in
> profiling Mono.
>
> What is the sample program that you need? Sorry but I really didn't
> understand what exactly you need.
The profiler today only runs when the program exists successfully, so we
need a shorter t
On Tue, 2006-10-31 at 22:52 +0100, Kornél Pál wrote:
> >Well, I'm not going to waste time with this thread anymore, since you are
> >not willing to understand or to cooperate. I asked for a program that takes
> >less than that to compile, because it's obvious that trying to profile that
> >is idiot
files in
trunk/vbnc/vbnc/tests.
Kornél
- Original Message -
From: "Alan McGovern" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, October 31, 2006 10:59 PM
Subject: Re: [Mono-dev] VBNC uses too much CPU and RAM on Mono
What he needs and i need and anyone else who wants to help
What he needs and i need and anyone else who wants to help with this issue needs is a program that takes 5-15 minutes to compile using VBNC. Trying to profile a 1 hour compile that crashes is a waste of time. Profiling for 10 minutes allows reasonalby fast results when testing a new patch. Making a
>Well, I'm not going to waste time with this thread anymore, since you are
>not willing to understand or to cooperate. I asked for a program that takes
>less than that to compile, because it's obvious that trying to profile that
>is idiotic and a complete waste of time. Is that so hard to get throu
On 10/31/06 Kornél Pál wrote:
> 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
>> 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
[Not approving the 700KB mail message to the list, just replying to some
comments here]
On 10/31/06 Kornél Pál wrote:
> >Does the code properly dispose the file strem objects as sson as
> >tokenization is done?
>
> http://svn.myrealbox.com/viewcvs/trunk/vbnc/vbnc/source/General/CodeFile.vb?rev=64
Is there a sample app the compiles slowly somewhere (and instructs on how to use VBNC) that i can download it and run a few tests myself to see if i could lend a hand? I'm interested in this kind of stuff, but probably won't be able to help much :p But i'll try.
Thanks,Alan.On 10/31/06, Ben Maurer
> On 10/31/06 Miguel de Icaza wrote:
>> > > Any help on speeding up vbnc is welcome.
>>
>> Ben got the impression that VBNC was keeping a linked list of all the
>> tokens after the tokenization phase (which is brutal on the GC as it
>> becomes a large link-list walk).
>
> While that is clearly a ve
On 10/31/06 Miguel de Icaza wrote:
> > > Any help on speeding up vbnc is welcome.
>
> Ben got the impression that VBNC was keeping a linked list of all the
> tokens after the tokenization phase (which is brutal on the GC as it
> becomes a large link-list walk).
While that is clearly a very ineffi
> > Any help on speeding up vbnc is welcome.
Ben got the impression that VBNC was keeping a linked list of all the
tokens after the tokenization phase (which is brutal on the GC as it
becomes a large link-list walk).
In my opinion, instead of having a tokenization phase that keeps all the
tokens
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 b
Hello,
Are you using latest svn for vbnc? A few optimization was committed this
week so it should be faster. If it is running out of memory though I think
there might some other problem optimizations won't resolve.
Rolf
On Sun, 29 Oct 2006 19:21:07 +0100, Kornél Pál <[EMAIL PROTECTED]> wrote
"Kornél Pál" <[EMAIL PROTECTED]>
Cc:
Sent: Sunday, October 29, 2006 8:44 PM
Subject: Re: [Mono-dev] VBNC uses too much CPU and RAM on Mono
Hey,
Even after the patches I suggested to Rolf, VBNC had a heap size of ~100mb
on MSFT. I'm a bit suprised Mono is having so much trou
but I may be wrong. Other than this problem I have no other idea,
> because it's running, but is slow and eats memory.
>
> Kornél
>
> - Original Message -
> From: "Rolf Bjarne Kvinge" <[EMAIL PROTECTED]>
> To: "Kornél Pál" <[EMAIL PROTEC
w and eats memory.
Kornél
- Original Message -
From: "Rolf Bjarne Kvinge" <[EMAIL PROTECTED]>
To: "Kornél Pál" <[EMAIL PROTECTED]>;
Sent: Sunday, October 29, 2006 7:37 PM
Subject: Re: [Mono-dev] VBNC uses too much CPU and RAM on Mono
> Hello,
>
> Ar
Hi,
Using the patch in
http://lists.ximian.com/pipermail/mono-devel-list/2006-October/021093.html
no exception ocurred in vbnc but I wasn't able to finish the resolve phase
because it runs out of memory. The machine I used has 1 GB RAM and is
running Windows XP. And I think such a machine shou
21 matches
Mail list logo
