[Labs-l] [Ops] Slowing down puppet runs?

Ryan Lane rlane32 at gmail.com
Sat Nov 1 18:30:10 UTC 2014


One thing that could be done is to keep a hash or version number on the
server of the current combination of repos that are responsible for puppet
runs. Whenever one of them changes, the version changes too. The clients
can check in with the server to see if they've already run the version on
the server. If not, just don't do a run. That would likely cut back on the
vast majority of all runs.

On Sat, Nov 1, 2014 at 11:01 AM, Marc A. Pelletier <marc at uberbox.org> wrote:

> On 10/31/2014 01:04 PM, Andrew Bogott wrote:
> > delays in the client run shouldn't really make a difference to anyone
> > who isn't actively debugging puppet and running things over and over by
> hand
>
> No, but a quick look at every graph of every instance shows significant
> spikes in resource usage every 20 minutes on the dot; it may not be
> currently harmful or problematic, but it's certainly a waste.
>
> -- Marc
>
>
> _______________________________________________
> Labs-l mailing list
> Labs-l at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/labs-l/attachments/20141101/dfe67a62/attachment.html>


More information about the Labs-l mailing list