search for: optree

...e pmap of a running mongrel says that by far the bulk of the memory immediately following launch is mapped anon / private for libruby.so, 23M libnkf.so 6M for kanji libsyck.so 7M for yaml I guess that is because Ruby is a dynamic language, and always allows for a running proc to modify the optree itself (''monkey patching''). So, in contrast to a compiled binary where the program code is all in the text seg, Ruby keeps the ''partly compiled bytecode'' optree in private heap, where each proc can mess with it at any time. My question is, how important is that...