That's disappointing. We'd be better off without any kind of pre-emption, only switching on I/O.
Jeff On Sun, Sep 11, 2011 at 9:44 PM, Steve <unetright.thebas...@xoxy.net> wrote: > The old 2.5/2.7 GIL hurts performance any time there is more than one thread > that is doing python work. Maybe you'd like to read up on how the old GIL > burns cpu time in excess signalling and failed lock acquisition: > http://www.dabeaz.com/python/NewGIL.pdf > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/KKh6yIezaVoJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
