Comments on: Puppet Memory Usage – not a fatality

By: Geert

Geert — Thu, 29 Jul 2010 10:06:24 +0000

This is exactly the reasons we opted for Cfengine. Despite a harder syntax resource consumption is way lower.

By: More Puppet Offloading

More Puppet Offloading — Sun, 21 Mar 2010 15:57:12 +0000

[...] already talked about offloading file sourcing in a previous blog post about puppet memory consumption. Here the idea is to prevent our puppetmasters to read the whole content of files in memory at once [...]

By: masterzen

masterzen — Fri, 29 Jan 2010 07:42:49 +0000

@Ohad,

Thanks!
I do also think cron is the best way to run puppetd. Puppetrun functionnality can be done in another way (ie mcollective comes to mind). Still you can get transient absurb memory consumption…

And we should definitely migrate reports to json/pson, and get rid of yaml…

By: Ohad

Ohad — Fri, 29 Jan 2010 02:55:25 +0000

excellent blog.
just yesterday a client tried to send a report with about 50MB of YAML (don’t ask why) which killed the puppetmaster (as the processes grow to 1.6gb!!).

nevertheless, I still recommend using cron for puppetd – i see very little benefits having a daemon just for puppetrun.

my 2 cents