Hi Pol,
Thanks for getting back to me.
On Sun, Nov 13, 2011 at 4:50 PM, Pol 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
Hi Pol,
Thanks for trying it again with threadsafe disabled and reporting back!
On Mon, Nov 14, 2011 at 4:32 AM, Pol wrote:
> 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 g
Hi Pierre,
On Tue, Nov 15, 2011 at 3:19 AM, Pol wrote:
> Hi Brian,
>
>> > 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
>> >
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 perform
On Mon, Nov 14, 2011 at 12:19 PM, Pol wrote:
> > But note that concurrent requests will *not* improve the utilization
> > of CPU-bound requests. Running multiple threads on the same CPU just
> > proportionally slows each thread down.
>
> That doesn't make sense: apps do a mix of CPU stuff and RPC
