Hum, best way to test it ? start 2 web2py instances with a cached query, let's say, and hit them with ab ? In theory the connection object to redis is itself a connection pool, so there won't be problems.
I always defined cache (and see it defined) in models, where it gets executed on every request.... is there a way to avoid class __init__ method (where the connection is built) on every request ?
