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