ActiveRecord probably isn't helping, but to really make it faster might require reframing the data model.
On Fri, Jan 23, 2009 at 12:07 AM, Ohad Levy <ohadl...@gmail.com> wrote: > >> > ah damnit. We've experimented with storeconfigs, and have been unable >> > to get it to scale, even with the significant improvements from >> > Brice's patches. >> > >> > I guess this is why external nodes can only set parameters and >> > classes as well. >> >> They're pretty much entirely orthogonal. The slowness in storeconfigs >> is the storage, but adding resources to the catalog at compile time is >> pretty cheap. >> >> This is now about five or six companies, at least, who really want >> StoreConfigs to be faster, but none seem to have the resources to >> actually spend time/money on it, which is frustrating. I expect that >> ActiveRecord isn't actually the right choice, and that it's >> straightforward (if tedious) to replace it with something else, but it >> does take time and commitment. I guess it's time to see if we can get >> some kind of bounty together to see if we can get multiple people to >> chip in to spend some time on it. I'd love to do it myself, but, >> well, I've gone down that road and gotten limited reward. > > What are the main problems you've encountered with ActiveRecord? as far as > I know from limited rails is that the latests version have a significant > performance improvements. > > Another point might be to enable some caching, (either locally) or split > the process between the client configuration retrieval and the > resource/facts update on the database. > > nevertheless, the main problem that I encountered is to support a high > availability database environment, thats the main reason we are not using > store config, we have a lot of different locations, and the database cant be > centralized in a "easy way". > > Thats why we've decided not to let puppet manage the database, rather then > we do it in the background (as we use it with our internal puppet rails > shiny web interface). > > I would love to see a way to inject values into the puppetmaster (maybe > similar to Luke usage of storing the mongrel ports number in his rails > module). > > my 2c. > > Ohad > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
