On Mon, 2009-10-19 at 12:01 +0200, Xavier Beaudouin wrote: > Hum... People there think it is use to mutch... more than 20% during a > run...
Remember something: you paid for that CPU, that means you want to use it as much as you can otherwise you paid for something you don't use. With that in mind, the optimal load on a server should be 100% CPU used :-) If those servers are not used or have room for 20% of CPU used by puppet, then it shouldn't matter, the kernel scheduler will do what it needs to allocate CPU to every running programs. If those servers are already 100% loaded, then that's an issue, and you might: * let puppet run less frequently or do CPU bound things less frequently * isolate what consumes CPU when doing a run (do you have unbounded execs?) * does your package manager consumes CPU? In my own experience, puppetd itself is usually more I/O bound (ie network and disk) than cpu bound, but since it depends entirely on what you have in your manifest, YMMV. > 2009/10/19 Ohad Levy <ohadl...@gmail.com> > puppet is usually not using too much of cpu.. (unless your > users are running on the puppetmaster ;)) > > maybe you can restrict the amount of things puppet do in each > run with the schedule metadata. > > How can I do that.. ? See: http://reductivelabs.com/trac/puppet/wiki/MetaparameterReference#schedule -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
