John Lorance wrote: > I've got a TG2 (2.0.3) application that is using memcache for beaker > caching and it generally works; however, under load I see strange > behaviour (see below). I'm leveraging Beaker caching via its method > decorator and only using it for caching (not for sessions). > > -beaker.lock_dir setting? does this apply to memcache? should this be > a NFS share in a farm environment? > Anyhow, I'm curious to understand more how the "lock_dir" setting > affects memcache types? In other words, if I am running a pair of > web servers and a pair of memcache servers, should I set this > "lock_dir" to an NFS share that everyone can see? I'm assuming beaker > is still using some disk based locking files and therefore, mutliple > servers would want to have acccess to them? Does this make sense? > If I'm reading the Beaker documentation correctly, yes, it's doing file-based locking for the memcache operations (NamespaceManager seems to be used throughout). That seems wrong for the memcache mode, as you point out, requiring either an NFS (or similar) share, or some other performance-killing mechanism.
I've tried to update the documentation describing Beaker Caching to describe memcache setup, but honestly I don't have a good solution for you here. Good luck, Mike -- ________________________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
