Yes, but the million dollar question is whether or not it really is superior with the I/O convoying problem in the current implementation (an effect that is substantially worse with the new GIL than with the old one by the way). Personally, I think the convoying issue is something that will have to be fixed eventually. Although, I also agree that it merits more study--especially with real-world applications. Cheers, Dave On May 19, 2010, at 3:34 PM, Martin v. Löwis wrote:

Peter Portante wrote:

...

Does anybody think that by having problems with the new GIL that it might further weaken the adoption rate for 3k? -peter

No, to the contrary. By having the new GIL being superior to the old implementation, the adoption rate for 3k will increase.

Regards, Martin

On Wed, May 19, 2010 at 4:17 PM, Peter Portante wrote:

Does anybody think that by having problems with the new GIL that it might further weaken the adoption rate for 3k? -peter

Nope, because the remaining issues with the new GIL affect the old GIL as well, and have yet to be proven to affect real world apps. My server is the only real world example I have seen and the modest 5% slow down it experiences on the new GIL & multi-core vs new GIL & single core can potentially be explained by other issues. The old GIL has a 25 to 30% slowdown on multi vs single core so over all the new GIL gives my server a 20% speed boost. Incremental upgrades to core functionality like the GIL is the better way to go then to try an optimize every facet of it before hand, because some of those optimizations may have unintended side effects in real world apps and if you attempt all the optimizations at once it makes it harder to figure out which is the cause of the unintended side effects.