Open Stack

Thanks Morgan.
In my embedded situation, There is no hard drive where I run the Openstack controller, keystone, and other control functions, thus, my only choice has to be to use an in-core-db (cache) for the realtime transactions into the database, and then use another process to sync the data into the real database cluster through network located off the controller node.

From: Dolph Mathews [mailto:dolph.mathews at gmail.com]
Sent: Monday, October 28, 2013 8:40 AM
To: OpenStack Development Mailing List
Cc: Morgan Fainberg
Subject: Re: [openstack-dev] distibuted caching system in front of mysql server for openstack transactions

It's not specific to mysql (or sql at all), but keystone is using dogpile.cache around driver calls to a similar effect.

  http://dogpilecache.readthedocs.org/en/latest/

It can persist to memcache, redis, etc.

  https://github.com/openstack/keystone/blob/master/keystone/common/cache/core.py

On Fri, Oct 25, 2013 at 6:53 PM, Qing He <Qing.He at radisys.com<mailto:Qing.He at radisys.com>> wrote:
All,
Has anyone looked at the options of putting a distributed caching system in front of mysql server to improve performance? This should be similar to Oracle Coherence, or VMware VFabric SQLFire.

Thanks,

Qing

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--

-Dolph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131028/57c93fb9/attachment.html>