On Tue, Jul 7, 2009 at 8:37 AM, Brice Figureau<[email protected]> wrote: > > On Tue, 2009-07-07 at 07:27 -0700, Nigel Kersten wrote: >> On Tue, Jul 7, 2009 at 7:20 AM, James Turnbull<[email protected]> >> wrote: >> > Sam Rowe wrote: >> >> Here's the ruby-bindings documentation for TC. There are several >> >> examples of different kinds of usage, the first one being a hash >> >> database. One other thing to point out is that I'm pretty sure TC >> >> doesn't use SQL and this might be a lot easier than you think. >> >> >> >> http://tokyocabinet.sourceforge.net/rubydoc/ >> >> >> >> One downside is that you'd be going from a fairly ubiquitous back-end >> >> to one that a lot of folks aren't familiar with. But hey, it's from >> >> Japan like Ruby and it's been going strong there for a long time and >> >> is considered very solid. >> > >> > Not being an expert on this and excuse me if this is a stupid question >> > ... :) If this essentially replaced a back-end RDBMS - is it easy for >> > people to query the data with other tools? For example, now I have my >> > database of stored configuration I can readily query it via SQL - how do >> > I get the same results with TC (can I?)? >> > >> > Secondly, how does it scale? Are there examples of large - and I >> > suspect someone on the list can fill in volumes statistics - hash >> > databases implemented in TC? We have some users who simply cannot use >> > stored configuration because it kills their installations as a result of >> > not scaling - Nigel at Google I am looking at you... :) >> >> hah. >> >> So I have to say, that 0.24.8 improved storeconfigs a lot. (awesome work >> Brice!) > > Thanks :-) > >> There is no observable performance hit with a single client puppeting >> against a single server with storeconfigs enabled or disabled anymore. >> Obviously capacity will decrease in a real world environment like >> ours, but it's much more feasible under 0.24.8 than it ever was >> before. >
> I don't know your (planned or real) usage pattern of storeconfigs but > mine is only for collected/exported resources. If you're in this case, > then the thin_storeconfigs pending patch would be a real killer for you. > And with queueing enabled, first client checking in is not an issue > anymore (or at least way less than it was before). So I'm not collecting or exporting resources, and honestly, I really only want facts in storeconfigs. The thin_storeconfigs patch is one I'm following with great interest, and the queuing of 0.25.x is brilliant. > -- > Brice Figureau > My Blog: http://www.masterzen.fr/ > > > > > -- Nigel Kersten [email protected] System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
