One thing to keep in mind is that if you'll deploy your webapp with Apache and mod_wsgi, there will be multiple processes running you app, and each one will have g object with its own cache. So a bit of memory wasted and possible data integrity issues: request A gets served by process A and updates/invalidates A cache , request B gets served by process B, assumes up-to-date cache but gets stale data. So in that setting cache should be stored somewhere external where it can be shared among processes. Like memcached or files.
On 8 febr., 17:20, Jonathan Vanasco <[email protected]> wrote: > i have some data that I cache on startup -- mostly config info and > misc database intensive stuff. > > i need to reload every so often. > > is it safe to reload it into g ? or should i cache this in memcached > or similar ? -- 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.
