Dan Sugalski <[EMAIL PROTECTED]> writes:

>                                             Bytecode files on-disk are
> shared across all the processes in the system, so you only get one
> in-memory copy of a file, which saves both RAM and load time if you're
> using a file that another process is using.

I assume this means that the plan is to mmap these files.  Are most
systems happy with hundreds (or thousands) of mapped sections of
memory or are there some negative performance implications of doing
that?

How about the code JITed from the bytecodes. Will it be shared?

Regards,
Gisle

Reply via email to