Yohanes Santoso wrote:
>   mallopt(M_MMAP_THRESHOLD, 0); /* declared in malloc.h */

Very interesting. I'd like to use this as a diagnostic.

I patched ruby's main.c to call mallopt() before anything else. It seems 
to be using a huge amount of memory, though. Is this normal? Starting 
the following:

$ ruby -e 'sleep 100'

Causes:

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
21422 vjoel     17   0  142m 140m 1892 S  0.0 13.9   0:00.62 ruby

I have 1.8.6p110 and ubuntu 7.04:

$ ruby -v
ruby 1.8.6 (2007-09-23 patchlevel 110) [i686-linux]
$ uname -a
Linux tumbleweed 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 
i686 GNU/Linux


-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407