On Sat, Feb 15, 2014 at 9:00 AM, Trevor Vaughan <tvaug...@onyxpoint.com>wrote:
> Wow, that's quite some dead thread resurrection! > > I remember this being discussed in the past and part of the issue is that > so many parts of what Puppet is doing are I/O bound so I'm not really sure > what the parallelism would gain you outside of destroying your I/O channels. > > That said, I think it would be nice to have supported for those that do > have systems that can take advantage of it. We may even see that a -j2 > would give just enough balance between I/O destruction and system > acceleration. > There was a recent, pretty in-depth discussion in puppet-dev about a related concept: batched application of resources: https://groups.google.com/forum/#!msg/puppet-dev/X7RgakTGnbk/19RgHTMuLZUJ > > Trevor > > > > > > > On Fri, Feb 14, 2014 at 11:52 PM, Andrew Pennebaker < > andrew.penneba...@gmail.com> wrote: > >> This is a fantastic idea! Any progress on this? >> >> >> On Sunday, March 4, 2012 10:53:23 PM UTC-5, Jon Forrest wrote: >>> >>> As many learning Puppet for the first time, the fact that the >>> order of actions is undefined unless specific metaparameters >>> like 'require' are used. Fine. >>> >>> This got me to thinking. The GNU make program has the "-j" >>> option, which allows make to start more than one action >>> in parallel if the actions are at the same dependency level. >>> I've used this option on a 48-core machine to great benefit. >>> >>> So, why can't there be a similar option in the puppet agent? >>> I can easily imagine how this could substantially reduce the >>> length of time for a puppet run. >>> >>> (The make "-j" option allows an optional numeric value, which, if >>> given, is the maximum number of actions that can be run >>> in parallel. If no numeric is given, then there's no limit >>> to the number of parallel actions). >>> >>> I did a quick review of the Puppet manual but I didn't see >>> anything like this. Am I missing something? Is this a good >>> idea? >>> >>> Cordially, >>> Jon Forrest >>> >>> -- >> 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+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/b836c960-09bc-48f5-8b5f-407d42233b10%40googlegroups.com >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Trevor Vaughan > Vice President, Onyx Point, Inc > (410) 541-6699 > tvaug...@onyxpoint.com > > -- This account not approved for unencrypted proprietary information -- > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CANs%2BFoV5iSNbuS%2BnxEzmU7mhQXzGtwf5p4-e4M3P1K_b_P_Fbw%40mail.gmail.com > . > > For more options, visit https://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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAOjOXY2Rv1i9s5fDtXf-w9o0%3DHtYzkbMkGc-1E0uSVGcZBFj_Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
