On Jan 9, 6:40 am, Tycon <[email protected]> wrote: > Does anyone have such a configuration working ? > > Basically it means that on every request nginx will use the URL as the > key to perform a lookup on memcached and serve the page from there if > it exists. If it's not cached then it will forward the request to > pylons which will produce the page and store it in mecached, so > subsequent request for the same page will be served by nginx using > mecached without forwarding the request to pylons. > > Also, the parts of the page that should not be cached (such as the > current user name, shopping basket, breaking news, etc) are handled > using SSI (server side include) which means that the page rendered by > pylons include a special SSI tag for each dynamic part of the page > (instead of the actual dynamic content). > > When nginx gets the page (either from pylons or memcached) it will > look for those special SSI tags and for each one it will issue a > request to pylons to render the dynamic part using the URL that is > specified in the tag. > > So the bottom line is that for each page only the dynamic parts of the > page will be rendered on each user request (dynamic parts are the ones > that can be different even for request for the same URL). As I > understand it from reading rails blogs, this is the holy grail of web > app frameworks, as it can give tremendous performance even on low end > hardware. At least it does on my development virtual machine.
I'm currently playing with Varnish as a caching layer, which has support for Edge Side Includes. Have you considered a setup like this? If so, I'd be interested to hear what made memcached + SSI more appealing. If not, I'd be happy to provide some links I've come across if you're interested in exploring this further. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
