lua-users home
lua-l archive

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

Florian Weimer wrote:
>>> Last time I looked at Python the interpreter used a single lock...
>> It's worse than that. Python's GIL is implemented so badly that you often
>> get worse performance by adding processors.
> I think this has been fixed. See
> <>

After reading far too many of the posts in that thread, I finally came
to this conclusion: They've cleaned up the lock itself, but it's still a
single lock (like Lua's lua_lock() macro). The speed-ups reported here:

are comparisons against the older implementation of the GIL (Global
Interpreter Lock, if you wondered), not against a single-threaded result.

So there's no performance gain with the threading (like there is with
luaproc when properly configured), but at least they can have efficient
blocking IO calls without blocking the application. That's something
that base Lua does not have.


The information contained in this email transmission may contain proprietary and business 
sensitive information.  If you are not the intended recipient, you are hereby notified that 
any review, dissemination, distribution or duplication of this communication is strictly 
prohibited.  Unauthorized interception of this e-mail is a violation of law.  If you are not 
the intended recipient, please contact the sender by reply email and immediately destroy all 
copies of the original message.

Any technical data and/or information provided with or in this email may be subject to U.S. 
export controls law.  Export, diversion or disclosure contrary to U.S. law is prohibited.  
Such technical data or information is not to be exported from the U.S. or given to any foreign
person in the U.S. without prior written authorization of Elbit Systems of America and the 
appropriate U.S. Government agency.