openstack team mailing list archive
Mailing list archive
Re: Caching strategies in Nova ...
+1 to DBs being slow. But what if we used a combo of memcache and db. Or
Anyone has experience on large deployments to see the kind of db traffic
we need to optimize for?
Another thing could be to avoid joins and then do sharding.
Behalf Of Brian Lamar
Sent: Friday, March 23, 2012 10:51 AM
Subject: Re: [Openstack] Caching strategies in Nova ...
On Mar 23, 2012, at 11:22 AM, Kevin L. Mitchell wrote:
> On Fri, 2012-03-23 at 08:55 -0300, Sandy Walsh wrote:
>> I don't doubt for a second the db is the culprit for many of our
>> The thing I like about internal caching using established tools is
>> it works for db issues too without having to resort to custom tables.
>> SQL query optimization, I'm sure, will go equally far.
> For that matter, I wouldn't be surprised if there were things we could
> do to nova's DB to speed things up. For instance, what if we
> non-SQL data stores?
Any database is going to be slow if you're talking to it more than
necessary. Even if we replaced MySQL with the latest and greatest
web-scale noSQL database out there we'd still be slow. I'd love to see a
combination effort of improving the flexibility of the DB layer as well
as improvements surrounding the sheer number of calls to the database.
> Kevin L. Mitchell <kevin.mitchell@xxxxxxxxxxxxx>
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp