On Wed, Oct 28, 2009 at 10:11 AM, Matt Feifarek <[email protected]> wrote: > I'm also getting frustrated with the speed. GAE is warning me that my pages > are taking too much cpu, and may blow my quota (I don't even have any users > yet; just testing things). And this is for a page with almost nothing... > just grab a record set, iterate through it and dump a one-line <p> into a > mako page. > So, maybe it's because Mako isn't caching? How has your experience been > actually running your tests? > I would imagine that some of the Pylons stack can be turned off in favor of > lower-level GAE stuff (static files, for example).
You should upload static files in app.yaml so they don't count against your quota. You can then disable the static file app in middleware.py. I don't know if the development server would then serve the static files, but since it's supposed to work just like the real server maybe it does. You can also disable other middlewares you're not using in middleware.py, such as sessions. I got the CPU warning too. I don't know if there's anything in Pylons' overhead that could be streamlined, or it's another thing that happens with all full-sized frameworks. Mako templates aren't cached because Mako can't write the files it normally would. I think it caches templates in memory for the lifetime of the app. You can replace Mako's TemplateLookup class with something that caches templates in Datastore or memcache. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
