It's IMO not the final users job to decide on such internal
details on the .prg level.
Of course not, but I´m my intention is have a way to easy test what is
the best value, without recompile Harbour each time.
Okay and sorry, in this case just put the C code inside
#pragma BEGINDUMP/ENDDUMP and include it in your test code.
Moreover it's specific to one of our possible MM choices,
so it cannot be made a generic Harbour setting. We should
also remember that we may want to switch MMs in the future.
I know, are there a way to detect if we are using dlmalloc ? If yes,
we can accept arguments from memtst.prg like:
memtest 10000
I guess that would mean too deep internal dependencies.
Przemek probably knows better.
Questions are:
- Which value of the three should be 10000?
Need be tested, my functions made such tests easy.
- Does it enhance performance for both XP and Vista, or just Vista?
Both, but bcc6.10 memory manager continues win in memtst. I need to
more accurate test to tell how is the best.
- Did you get your results using a specific app or our
speed testing tools?
Only memtst. But I see in my final app that using dlmalloc it is more
slow than native bcc 6.10 mm.
- If it was an app, was it a GUI, and with which GUI framework?
I use FWH only.
Thanks, and inform us about your further results.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
