Hi, Brian, Gregory Thanks for your valuable insights! I did know about the issue 6323 and had stared it. However I was not sure it was the same as the issue mentioned CPU bound requests. My app is very much RPC bound. I've added a comment to this thread to the issue and I've set threadsafe: no and will monitor. So far latency seems Ok and the number of instances is 5x-6x of when I had threadsafe: yes. I do agree with Felippe, we should be able to maintain the 50% discount until python27 and threadsafe are fully supported. This is also making things worse - it seems the minimum latency is not being enforced correctly, I also have this. http://code.google.com/p/googleappengine/issues/detail?id=5765&can=5&sort=-status&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log
Sérgio On Dec 7, 5:12 am, "Gregory D'alesandre" <[email protected]> wrote: > Hi Felippe, > > As you noted Python 2.7 is released. While Python 2.7 is still > experimental it is working well for some but indeed there are still issues > before it will be fully GA. There was a concern that we were abandoning > Python because there was no solution for concurrent requests. Python 2.7, > even in its current state, shows that we are not abandoning Python. We > tried our best to make appropriate trade-offs with the new pricing model > but at some point we needed to roll it out for the reasons we've discussed > at length in the past. For instance, when this was written we were also > going to launch the new pricing 1.5 months earlier than we actually > released it, which likely saved you quite a bit of money, as opposed to > this which is costing you more. > > While my guess is you'd still rather that the 50% discount persisted I hope > that answers your question, > > Greg > > On Tue, Dec 6, 2011 at 5:29 PM, Felippe Bueno <[email protected]>wrote: > > > > > > > > > > > On Tue, Dec 6, 2011 at 8:56 PM, Brian Quinlan <[email protected]> wrote: > > >> There is a known bug where the combination of Python 2.7 and enabling > >> concurrent requests causes large latency increases. The Python 2.7 > >> runtime is still experimental and bugs like this are expected. > > > Ok, I understand that. > > > Greg, could you please let us know why we have the new full-sized instance > > hour for python and still not have python concurrent requests ? > > > I'm asking because you > > wrote<http://groups.google.com/group/google-appengine/browse_thread/thread/...> > > : > > > Q: Will there be a solution for Python concurrency? Will this require any > > code changes? > > Python concurrency will be handled by our release of Python 2.7 on App > > Engine. We’ve heard a lot of feedback from our Python users who are > > worried > > that the incentive is to move to Java because of its support for > > concurrent > > requests, so we’ve made a change to the new pricing to account for > > that. *While > > Python 2.7 support is currently in progress it is not yet done *so we > > will be ** > > providing a half-sized instance for Python (at half the price) until > > Python > > 2.7 is released.* * > > > Ok, I know. It was already released (as experimental), but I thought that > > the purpose to holding "full-sized instances" was to give to python users > > the concurrent requests. > > > Thanks > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
