You may already know this but there is discussion of memory allocation in perldoc perlguts.
It is suggested that you enable the version of malloc that is dis- tributed with Perl. It keeps pools of various sizes of unallocated memory in order to satisfy allocation requests more quickly. However, on some platforms, it may cause spurious malloc or free errors.I have found cases where perl's alloc doesn't play well in a threaded application. We had to revert to the OS alloc functions. Unfortunately if you use the OS alloc function, you will loose some very valuable debugging features. perldoc Devel::Peek.
Mr. Rock, please meet Mr. Hard Spot.
In reply to Re: General memory management for embedded/extended perl with C threads
by osunderdog
in thread General memory management for embedded/extended perl with C threads
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |