The GIL (old or new) is not a problem for concurrency unless your application spends large quantities of time CPU-bound. As soon as you make an I/O request, some other thread will run. The GIL doesn't hurt.
Jeff On Sat, Sep 10, 2011 at 4:04 PM, Steve <unetright.thebas...@xoxy.net> wrote: > I (and many others I think) have been frustrated with how instance hours > billing can explode in the face of traffic spikes. I've submitted Issue > 5858 to help us put a hard limit on that scaling out. Regardless, it is > quite clear that the only real hope is to implement multi-threaded request > handling. Java has that option and the new Pytohn 2.7 runtime is supposed > to bring that. Seeing how important concurrent handling is going to be to > keeping bills reasonable, it's a real shame that the Python's New-GIL > improved concurrency was rejected for Python 2.7 in part to keep encouraging > adoption of 3.X. > > -- > 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/-/qui7GhQvcCcJ. > 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.
