On Fri, 20 Nov 2009, Szak�ts Viktor wrote: Hi,
> I'd say go for it. I'll commit it in a while. > Any reason we don't seem to have HB_FM_DLMT_ALLOC > enabled by default when building vmmt lib? I think > we should enable it. For all platforms which now uses DLMALLOC I think it can be enabled. For sure for 64bit builds. Using many mspaces on 32bit platforms may cause memory fragmentation. For 99% of programs it should not be a problem but if someone created code which allocates very large memory blocks containg hundreds of megabytes then it may create problems. On 64bit platforms the address space is large enough to fully eliminate this problem. There is also yet another problem with DLMALLOC. Valgrind does not recognize it so it cannot create some memory statistics when it's used instead of default memory manager which is replaced dynamically by valgrind. It means that for Linux it should be optional. Anyhow I've just made some test with suse11.2-...@64 and DLMALLOC compiled with hvmall.c is noticeable faster then default memory manager and speed difference is quite huge (~15% in speedtst.prg). so in some cases it can be important extension for final code. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
