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 sept. 2016 à 22:50, <webmas...@trytha.com> a écrit :

> 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 Tuesday, September 13, 2016 at 11:57:11 AM UTC-7, Mathieu Clabaut wrote:
>
>> 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
>> than 10s response time ! ), and I have to address this difficulty first…
>>
>> On Tue, Sep 13, 2016 at 4:16 PM <webm...@trytha.com> wrote:
>>
> 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 UTC-7, Niphlod wrote:
>>>>
>>>> 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, the password reset
>>>>> feature stopped working, as I detail here:
>>>>> https://groups.google.com/forum/?pli=1#!topic/web2py/YndwuzoEypw
>>>>>
>>>>> And today I decided to try out the latest version (2.15.x based on
>>>>> changelog) from Git to see if you all had maybe fixed it, but using a
>>>>> completely fresh install from Git made it so my local GAE environment 
>>>>> can't
>>>>> even access the DB for some reason.  For reference, I was previously using
>>>>> web2py version 2.14.6, which has a working DAL connection but the password
>>>>> recovery doesn't work.  The associated DAL version is 16.03.  Here is the
>>>>> error when trying to connect to the DB (app name and id are obfuscated):
>>>>>
>>>>> ERROR    2016-09-13 06:31:57,189 restricted.py:171] Traceback (most
>>>>> recent call last):
>>>>>
>>>>>   File "/home/www-data/web2py/gluon/restricted.py", line 220, in
>>>>> restricted
>>>>>
>>>>>     exec(ccode, environment)
>>>>>
>>>>>   File "/home/www-data/web2py/applications/<app-name>/models/db.py",
>>>>> line 73, in <module>
>>>>>
>>>>>     db = DAL('google:sql://<app-id>:live/<app-name>', migrate=True) #
>>>>> DEBUG REVIEW: Turn off after migrations.
>>>>>
>>>>>   File "/home/www-data/web2py/gluon/packages/dal/pydal/base.py", line
>>>>> 170, in __call__
>>>>>
>>>>>     obj = super(MetaDAL, cls).__call__(*args, **kwargs)
>>>>>
>>>>>   File "/home/www-data/web2py/gluon/packages/dal/pydal/base.py", line
>>>>> 475, in __init__
>>>>>
>>>>>     "Failure to connect, tried %d times:\n%s" % (attempts, tb)
>>>>>
>>>>> RuntimeError: Failure to connect, tried 5 times:
>>>>>
>>>>> Traceback (most recent call last):
>>>>>
>>>>>   File "/home/www-data/web2py/gluon/packages/dal/pydal/base.py", line
>>>>> 455, in __init__
>>>>>
>>>>>     self._adapter = adapter(**kwargs)
>>>>>
>>>>>   File
>>>>> "/home/www-data/web2py/gluon/packages/dal/pydal/adapters/__init__.py", 
>>>>> line
>>>>> 40, in __call__
>>>>>
>>>>>     obj = super(AdapterMeta, cls).__call__(*args, **kwargs)
>>>>>
>>>>>   File
>>>>> "/home/www-data/web2py/gluon/packages/dal/pydal/adapters/google.py", line
>>>>> 40, in __init__
>>>>>
>>>>>     super(GoogleSQL, self).__init__(*args, **kwargs)
>>>>>
>>>>>   File
>>>>> "/home/www-data/web2py/gluon/packages/dal/pydal/adapters/base.py", line
>>>>> 373, in __init__
>>>>>
>>>>>     super(SQLAdapter, self).__init__(*args, **kwargs)
>>>>>
>>>>>   File
>>>>> "/home/www-data/web2py/gluon/packages/dal/pydal/adapters/base.py", line 
>>>>> 51,
>>>>> in __init__
>>>>>
>>>>>     self._initialize_(do_connect)
>>>>>
>>>>>   File
>>>>> "/home/www-data/web2py/gluon/packages/dal/pydal/adapters/google.py", line
>>>>> 49, in _initialize_
>>>>>
>>>>>     super(MySQL, self)._initialize_(do_connect)
>>>>>
>>>>>   File
>>>>> "/home/www-data/web2py/gluon/packages/dal/pydal/adapters/base.py", line 
>>>>> 64,
>>>>> in _initialize_
>>>>>
>>>>>     self._find_work_folder()
>>>>>
>>>>>   File
>>>>> "/home/www-data/web2py/gluon/packages/dal/pydal/adapters/google.py", line
>>>>> 44, in _find_work_folder
>>>>>
>>>>>     super(GoogleSQL)._find_work_folder()
>>>>>
>>>>> AttributeError: 'super' object has no attribute '_find_work_folder'
>>>>>
>>>>>
>>>>> Version 2.12.2 has neither of these problems.  Please help!  I want to
>>>>> use the latest versions!
>>>>>
>>>> --
>>> Resources:
>>> - http://web2py.com
>>> - http://web2py.com/book (Documentation)
>>> - http://github.com/web2py/web2py (Source code)
>>> - https://code.google.com/p/web2py/issues/list (Report Issues)
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "web2py-users" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to web2py+un...@googlegroups.com.
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to