Additionally, from a performance perspective, we couldn't even run the test suites we run with PuppetDB against the ActiveRecord based system. It falls over, we run out of memory and the slowness is unreal. If you want to see this in action, Look for "PuppetConf Deepak" on youtube and you'll see talks where he shows this in live demos.
Beyond that, Ruby (MRI at least) take more memory than many PuppetDB installations. I was never a huge fan of the JVM, but when I saw what PuppetDB could do with only a 128MB heap, I was sold. It's a constant memory reservation from the OS, and just works. MRI would jump from little usage to hundreds of megs (even sometimes gigs) of memory during runs and checkins from clients. Another advantage of the JVM is are the metrics you can get from it to do things like tuning and monitoring all via JMX. If the API is the main concern, there are binding for the API in python, ruby, go, even haskell. There are probably lots more I'm just not aware of. >From an installation point of view (your heavy comment) installing a jar and jre isn't too difficult. (We even provide a module to do this for you). It's also a little easier to ensure dependencies all work together compared to Ruby with ActiveRecord versions changing/breaking API between 2.x, 3.x and 4.x. Also, after 3.x, active record started requiring many more gems, IIRC. If there are specific problems, I'm sure somebody would be happy to help you a bit. If you only have complaints, I hope some of this is food for thought. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAMto7LL01OivipRv1GhfT932wJO-LtddcFVa96TqXxheDn1KXw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
