[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Why nobody talks about Lua
- From: Florian Weimer <fw@...>
- Date: Mon, 15 Feb 2010 19:03:03 +0100
* Tony Finch:
> On Sun, 14 Feb 2010, Gé Weijers wrote:
>>
>> Last time I looked at Python the interpreter used a single lock to make sure
>> that no two threads could be running inside the interpreter at the same time.
>> Python supports threads by serializing them. That helps with using blocking
>> system calls but not with performance.
>
> It's worse than that. Python's GIL is implemented so badly that you often
> get worse performance by adding processors. http://blip.tv/file/2232410
I think this has been fixed. See
<http://mail.python.org/pipermail/python-dev/2009-October/093321.html>
and subsequent threads.
- References:
- Why nobody talks about Lua, Alex Combas
- Re: Why nobody talks about Lua, Alex Combas
- Re: Why nobody talks about Lua, dcharno
- Re: Why nobody talks about Lua, Alexander Gladysh
- Re: Why nobody talks about Lua, Alex Combas
- Re: Why nobody talks about Lua, Alexander Gladysh
- Re: Why nobody talks about Lua, steve donovan
- Re: Why nobody talks about Lua, Alexander Gladysh
- Re: Why nobody talks about Lua, Eike Decker
- Re: Why nobody talks about Lua, steve donovan
- Re: Why nobody talks about Lua, Alexander Gladysh
- Re: Why nobody talks about Lua, Gé Weijers
- Re: Why nobody talks about Lua, Tony Finch