2009/12/4, Michal Rudolf <mrud...@kdewebdev.org>: > 2009-12-04 07:52:58, Pascal Georges: >> > We all should ignore your remark above: Memory is not consumed because >> > of fragmentation. >> >> Ignore my remark if you want to (I love the kind of wording "We all >> should >> ignore your remark above"), but I confirm that the memory used (reported >> as >> virtual memory used by a process) increases due to memory fragmentation. >> After a while the holes in memory slots tend to cease their increase, >> because the allocation algorithm manages to reuse them. Look at >> differences >> in Tcl alogrithm and glibc sources to understand the differences. > Pascal, does it mean that Tcl uses internal memory management, so for the > system some memory looks as used, even though internally it is marked as > free?
Yes. And Tcl memory management is better than the libc one. This is why a Tcl maintainer (from Evolane company) suggested to me to switch to Tcl API instead of classical malloc & new. See operator overloading in C++ code (new & delete calls). Note that Tcl has an overhead of 8 kB for each memory chunck but of course is smart enough at reusing free parts of chuncks of memory. I only switched to Tcl API on Pocket PC because on PC you usually don't care about a small exra amount of RAM wasted. Pascal ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
