lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


On Wed, Apr 18, 2012 at 11:11 AM, Michal Kottman <k0mpjut0r@gmail.com> wrote:
> You can alleviate this problem by going multi-process instead of
> multi-thread.

i think this is the 'right' answer; but still there are advantages to
the threaded model.  from the Lua perspective the isolation is the
same, as it can only communicate via C modules, but the C part is
easier when you have all Lua states in the same memory space.

maybe a different approach could be a compile-time flag for LuaJIT,
when active it would allocate string and userdata content out of the
2GB region, so the limit would be 2GB for structure and 'small'
objects.  big data chunks would be able to grow to the full memory
available.  Of course, this assumes that the metadata parts of strings
and userdata reference the content by a pointer, and are not adjacent
on a single-allocated block.

-- 
Javier