haaaaalt!. Either you use web2py (and we can help with that) OR nginx (and you'll need to cfr THEIR support for a proper config). There's no facility whatsoever for web2py to cache the object and for nginx to fetch it from the same memcached instance.
That being said, using cache.ram in multiprocess environment is OF COURSE pitfalled because each process would be need to be hit the first time, so what you're observing with cache.ram is entirely expected. Once you choose to store the cached object in some external backend (disk, redis, memcache), the "pitfall" is closed, but you don't need any additional nginx configuration. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
