The poor performance is not a configuration problem, web2py must be
modified to cache the compiled code of models, views and controllers
instead of reading, parsing and compiling them on every request.
But, there is a configuration problem with the static files config in
app.yaml.
- url: /(?P<a>.+?)/static/(?P<b>.+)
static_dir: applications/\g<a>/static/\g<b>
The static_dir directive cannot use pattern matching:
http://code.google.com/appengine/docs/configuringanapp.html#Static_File_Handlers
- url: /images
static_dir: static/images
- url: /images/(.*)
static_files: static/images/\1
upload: static/images/(.*)
To use pattern matching on static files, use the static_files with
upload directive instead. The static files will be served by google's
static file servers instead of the web2py application server.
Robin
On Oct 22, 11:40 pm, mdipierro <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Yarko and I and whoever wants to help are working on a registration
> app for PyCon2009. Although we are not planning to run it on GAE we
> have a copy running on GAE:
>
> http://web2py.appspot.com/web2conf
>
> We could use some testings.
>
> The sourse is on launchpad (web2conf). Requires the latest plugin_t2
> which is also on launchpad.
>
> @Robin, the average requests takes 800ms and I do not think GAE is
> caching the gluon/* modules. Is there any configuration that we should
> do to bring down the time?
>
> Massimo
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" 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/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
