Just from experience. They do a great job. But the killer thing about caching is how u do the cache invalidation.
Just caching stuff is easy-peasy, making sure it is invalidated on all servers in all conditions, not so easy... On 3/22/12 4:26 PM, "Sandy Walsh" <sandy.wa...@rackspace.com> wrote: We're doing tests to find out where the bottlenecks are, caching is the most obvious solution, but there may be others. Tools like memcache do a really good job of sharing memory across servers so we don't have to reinvent the wheel or hit the db at all. In addition to looking into caching technologies/approaches we're gluing together some tools for finding those bottlenecks. Our first step will be finding them, then squashing them ... however. -S On 03/22/2012 06:25 PM, Mark Washenberger wrote: > What problems are caching strategies supposed to solve? > > On the nova compute side, it seems like streamlining db access and > api-view tables would solve any performance problems caching would > address, while keeping the stale data management problem small. > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
