[antlr-interest] BENCHMARK. ANTLR. Bad results.

[Ruslan Zasukhin]

On 11/13/04 5:10 PM, "John D. Mitchell" <johnm-antlr at non.net> wrote:

>>>>>> "Ruslan" == Ruslan Zasukhin <sunshine at public.kherson.ua> writes:
> [...]
> 
>> Yes right. Btw, our benches was on Visual.  Aslo we will make with
>> CodeWarrior.
> 
>> CodeWarrior already have built-in manager for new, And CodeWarrior's new
>> is much faster of Visual's.  Aha. So on CW we can expect better results.
> 
> Has the world changed in more recent versions of MS Windows internals?

> Certainly historically, the MS memory allocator was truly atrocious in
> terms of performance.  Especially as churn and memory pressure increase.

This is not issue of Windows internals!

If you look into sources of Visual libs, you will see that

    ::operator new()

Simply calls malloc().

This was in Visual 6.0 and it still in 7.x

In the CodeWarrior they use behind the operator new the whole Heap Manager,
Similar to one discussed in Stroustrup's book. CodeWarrior take care about
small objects and so on.


-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/antlr-interest/

<*> To unsubscribe from this group, send an email to:
    antlr-interest-unsubscribe at yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/