>Hi Toninho, > >IMO, these values should be preconfigured by Harbour (at >compile time or runtime) for best values decided by the >development team's (our) best judgement and at most offered >as overrides for defaults in the form of build-time tuning >or internal cmdline options (but I'd even avoid that, too). Hi Viktor, I agree
>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. >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 >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 best regards, Toninho. ] __________________________________________________ Faça ligações para outros computadores com o novo Yahoo! Messenger http://br.beta.messenger.yahoo.com/ _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
