On Wed, Oct 28, 2009 at 3:46 PM, Mike Orr <[email protected]> wrote:
> You can also disable other middlewares you're not using in > middleware.py, such as sessions. > Sessions are stored in datastore by buffet, right? Wouldn't one want to keep sessions? (I suppose it depends on the app, but most non-trivial apps need session...) 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. > Yeah, TBD. It seems that Pylons really is built around paster, which keeps things "hot". To build-up and tear down the whole stack each hit (like "oneshot" in the old Webware days) will always be slow. 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. I was aware of the file issue, but thought that maybe it could cache somewhere else (you're alluding to that possibility). Perhaps lots of Buffet caching is in order. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
