LOL. I am using it at camio.com we have a lot of internal dashboards based
on web2py and large number of datasets BUT we bypass web2py Auth because
have a different mechanism so we did not notice this problem. I will check
but I often test GAE before posting new versions.
On Tuesday, 13
Indeed, I did my test on a single instance with no scaling in order to
characterise the cost if the service becomes largely used.
You are right, with automatic scaling, the response time is totally
acceptable. The cost is also acceptable as least until the site usage keeps
low...
Le mar. 13
Hi Mathieu! Are you using the default instance_class in your app.yaml? I
felt GAE was running a bit slow, but upgrading to the F2 instance_class
really improved overall response for a very minor increase in cost. I'd be
interested to see what scaling options you have set in the app.yaml.
On
I also do, but didn't try further than 2.14.6 + some git revisions…
And it makes me realized I still have no test for password reset… I'll add
some !
For now I have quite bad performances on GAE (3 requests / seconds for one
instance when facing 20 simultaneous simulated users → leads to more
I'm using it! It's very solid except for these two current issues. It'd
also be nice if there were some (any) documentation regarding how to use it
with Google Cloud Storage and Google Datastore while also using Google
Cloud SQL. www.trytha.com
On Tuesday, September 13, 2016 at 2:47:43 AM
I absolutely love when the most used by big guys backend seems to fail for
the most basic reasons...is someone really using web2py on GAE or it's just
for show ?
On Tuesday, September 13, 2016 at 9:02:19 AM UTC+2, webm...@trytha.com
wrote:
>
> First, sometime around the 2.13 or 2.14 change,
6 matches
Mail list logo
