[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Tables and multithreading
- From: Mark Hamburg <mhamburg@...>
- Date: Mon, 20 Mar 2006 09:02:19 -0800
on 3/16/06 4:06 AM, Javier Guerra at email@example.com wrote:
> the downside is that there's a single big lock for each LuaState, not one for
> each lua object, so the concurrency is pretty low.
The lock is also acquired and released with high frequency if you spend much
time calling C code (including the standard Lua library) and even without
contention this tends to sap performance on a multi-processor machine
because it forces lots of instruction and memory syncs.