On Wed, 02 Mar 2011, Ron Pinkas wrote:

Hi Ron,

> Many thanks for the detailed and insightful notes. It was indeed
> very curious to accept that a sub minor version would break
> performance in a product of this nature.
> BTW, do you know of a reason why HB_FM_DL_ALLOC should not be set by
> default?

In Windows and OS2 IMO it should be enabled by default.
It nicely improves the speed and resolves very serious problems
with some native C memory managers, i.e. in BCC.
Please only remember that some compilers may not allow to cleanly
replace default memory manager and it's necessary to set USE_DL_PREFIX
for them.
In Linux and some other systems default memory manager are already
DLMALLOC based (i.e. PTMALLOC) so it's already here. Some systems
like OpenSuse already has very good MM optimized for concurrent use
in MT programs (Hoard Memory Allocator).
Anyhow using DLMALLOC still gives speed improvement but it has one
side effect: VALGRIND cannot replace our own DL MALLOC with his own
MM so it cannot follow allocated memory.
These are the main reason why DLMALLOC is not enabled be default in
Harbour *nix builds though I very often use it in my custom builds
when I do not need to use valgrind.

best regards,
Przemek

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
xHarbour-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xharbour-developers

Reply via email to