On Sunday, September 11, 2011 3:27:43 PM UTC-7, Jeff Schnitzer wrote: > > 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 my GET requests, I/O accounts for roughly half of the time to process the request. When a user POSTs new data, my app does a fair amount of recalculations and I/O is only about 20% of the request processing time. So 50% of my GETs and 80% of my POSTs would benefit from the improved concurrency of the new GIL. Cheers, Steve -- 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/-/DHKRXZZF3v0J. 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.
