memcache is a storage engine that web2py can use to cache selects. Both memcache or redis are faster than cache.ram or cache.disk (especially with concurrent access): those are "pure-python" solutions embedded in the framework.
On Monday, January 27, 2014 3:50:36 PM UTC+1, Tito Garrido wrote: > > Hi Folks, > > I am planning a new application and I am wondering, should I use memcache > instead of cache selects? > > Do I need to use memcache if I am using cache select? Which one is faster? > What is the best practice? > > The plan is to cache some selects to show in view and get a fast response > time. > > Thanks in advance, > > Tito > > -- > > Linux User #387870 > .........____ > .... _/_õ|__| > ..º[ .-.___.-._| . . . . > .__( o)__( o).:_______ > -- 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/groups/opt_out.
