Half sized instances, so they may be half speed. -----Original Message----- From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Pol Sent: Sunday, November 13, 2011 9:32 AM To: Google App Engine Subject: [google-appengine] Re: Help resolve massive performance regression in 2.7 vs 2.5 runtime
Hi Brian, It helps, it's now at ~5s instead, but still at least 2x slower than on the 2.5 runtime. So on December 1st, the 50% discount for front-instances is gone. The idea is to compensate by switching to Python 2.7 with multithreading, but it looks like at this point it's a lose-lose situation: it runs more requests at the same time, but they take longer. We're mid- November already, do you guys think you'll have all of this working perfectly within 2 weeks? The 1.6 SDK which actually allows to run 2.7 locally was just released, so we're only starting to test now. Seems to me deferring the payment change 1 more month to January 1st 2012 wouldn't hurt :) On Nov 12, 10:09 pm, Brian Quinlan <bquin...@google.com> wrote: > Hi Pol, > > Thanks for getting back to me. > > On Sun, Nov 13, 2011 at 4:50 PM, Pol <p...@everpix.net> wrote: > > Hi Brian, > > > threadsafe is "true" > > There is a known issue where concurrent requests (enabled with > threadsafe) can be much slower than non-concurrent requests, > especially if the request is CPU-bound. > > You might want to set threadsafe to "false" and see if that fixes the problem. > > Cheers, > Brian > > > > > > > > > Here's an example password_hash for an original 8 characters password: > > > $2a$04$cbM2uHwDphIG3jFFRpq1mui5aVjevnDUwhvQ77S/WG/qvJMpiXAL6 > > > On Nov 12, 6:58 pm, Brian Quinlan <bquin...@google.com> wrote: > >> Hi Pol, > > >> On Sun, Nov 13, 2011 at 1:48 PM, Pol <p...@everpix.net> wrote: > >> > Hi, > > >> > Since switching to 2.7 runtime, logging in > >> > tohttp://www.everpix.com went from about a second to anywhere > >> > from 15s to 60s. I tracked it down to this single password checking line: > > >> > from bcrypt import bcrypt > >> > bcrypt.hashpw(password, self.password_hash) == self.password_hash > > >> What value are you using for "threadsafe" in your app.yaml? > > >> How large is self.password_hash? > > >> Cheers, > >> Brian > > >> > This comes from "a native Python implementation of the py-bcrypt > >> > package fromhttp://www.mindrot.org/projects/py-bcrypt/"; grabbed > >> > from here:https://github.com/erlichmen/py-bcrypt. > > >> > So what's happening here and how can we fix this? > > >> > Thanks, > > >> > - Pol > > >> > -- > >> > 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 athttp://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 athttp://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. -- 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.
