Hi, I''m using PuppetDB with builtin backend, haven''t switched yet to postgresql, and I''m starting to see decrease in performance of my agent runs. I use PuppetDB solely because of exported resources support. How soon should I think about moving to PostgreSQL? How many clients does my master need to serve, so that PuppetDB in it''s default installation, without pgsql, becomes a bottleneck? What''s you''re experience? Thank you, -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at groups.google.com/group/puppet-users?hl=en. For more options, visit groups.google.com/groups/opt_out.
I would recommend moving it over now. There are magic numbers I could make up about when to switch etc., but if you want to get it right from the beginning switch now. The problem is HSQLDB stores everything in the RAM in the JVM, and as that gets bigger your JVM garbage collection consumes more CPU etc. and you''ll always be increasing your JVM heap also ... Not only that, PostgreSQL will be better for backups, outside querying, better monitoring and will allow you more performance tuning opportunities. On Wed, Feb 6, 2013 at 8:20 PM, Jakov Sosic <jsosic@gmail.com> wrote:> Hi, > > I''m using PuppetDB with builtin backend, haven''t switched yet to > postgresql, and I''m starting to see decrease in performance of my agent > runs. > > I use PuppetDB solely because of exported resources support. > > > How soon should I think about moving to PostgreSQL? How many clients > does my master need to serve, so that PuppetDB in it''s default > installation, without pgsql, becomes a bottleneck? What''s you''re experience? > > > Thank you, > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at groups.google.com/group/puppet-users?hl=en. > For more options, visit groups.google.com/groups/opt_out. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at groups.google.com/group/puppet-users?hl=en. For more options, visit groups.google.com/groups/opt_out.
Jakov Sosic
2013-Feb-06 23:22 UTC
Re: [Puppet Users] PuppetDB builtin backend performance?
On 02/06/2013 09:48 PM, Ken Barber wrote:> I would recommend moving it over now. There are magic numbers I could > make up about when to switch etc., but if you want to get it right > from the beginning switch now. > > The problem is HSQLDB stores everything in the RAM in the JVM, and as > that gets bigger your JVM garbage collection consumes more CPU etc. > and you''ll always be increasing your JVM heap also ... > > Not only that, PostgreSQL will be better for backups, outside > querying, better monitoring and will allow you more performance tuning > opportunities.Thank you, I will migrate as soon as I get some spare time to work on infrastructure. -- Jakov Sosic srce.unizg.hr -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at groups.google.com/group/puppet-users?hl=en. For more options, visit groups.google.com/groups/opt_out.
If you like, try the puppetdb module ... it includes support for setting up the postgresql server as well: forge.puppetlabs.com/puppetlabs/puppetdb We''re really working hard to make it work well (and the postgresql module for that matter) and would love to hear if it works well for you. On Wed, Feb 6, 2013 at 11:22 PM, Jakov Sosic <jsosic@srce.hr> wrote:> On 02/06/2013 09:48 PM, Ken Barber wrote: >> >> I would recommend moving it over now. There are magic numbers I could >> make up about when to switch etc., but if you want to get it right >> from the beginning switch now. >> >> The problem is HSQLDB stores everything in the RAM in the JVM, and as >> that gets bigger your JVM garbage collection consumes more CPU etc. >> and you''ll always be increasing your JVM heap also ... >> >> Not only that, PostgreSQL will be better for backups, outside >> querying, better monitoring and will allow you more performance tuning >> opportunities. > > > Thank you, I will migrate as soon as I get some spare time to work on > infrastructure. > > > -- > Jakov Sosic > srce.unizg.hr > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at groups.google.com/group/puppet-users?hl=en. > For more options, visit groups.google.com/groups/opt_out. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at groups.google.com/group/puppet-users?hl=en. For more options, visit groups.google.com/groups/opt_out.