One more thing to keep in mind, the more templates you are compiling also adds to time.
On Sat, Jan 28, 2012 at 11:11 AM, Antidot SAS <antidot...@gmail.com> wrote: > Thx for answering, I really appreciated your investment, you gave some > serious lead to search, I'll see on Monday and let you know if something > comes up. As far as swapping, no sign on the server. > > > > > On Fri, Jan 27, 2012 at 11:40 PM, jcbollinger <john.bollin...@stjude.org> > wrote: >> >> >> >> On Jan 27, 11:10 am, Antidot SAS <antidot...@gmail.com> wrote: >> > Here are the info you wanted: >> > OS: Debian squeeze >> > Puppet: installed from gem version 2.7.9 >> > As I sayed the hardware is an old Poweredge SC1425 with 4 Xeon 2,8 Ghz >> > with >> > 2 Go of Memory >> > >> > Apparently the code is preety ugly since the compiled time is big, I >> > have >> > just share the code:https://github.com/jmauro/puppet-user >> >> >> The code is pretty, but very complicated, especially for the >> relatively simple job it seems to be trying to do. Clearly that code >> is not your first cut at this, so did older versions exhibit the same >> poor compile times? If you go back through your revision history, >> perhaps you can find the change that made compile times spike. >> >> Also, Brice's suggestion to check for swapping is a good one, >> especially because Puppet sometimes uses a lot of memory. Although >> your hardware is a bit old, it should be up to this task so long as it >> hasn't too many competing demands on it. >> >> Since your catalog eventually does compile, it might be useful to look >> at the result, available in YAML form. You might discover that it is >> a lot more complicated than you thought, and that would yield clues to >> what needs to be cut back. >> >> If all else fails, try disabling as much of the code as possible, then >> watch compilation times as you re-enable it bit by bit. I suspect >> that you will find some particular part that consumes the lion's share >> of the compilation time. >> >> >> John >> >> -- >> 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. >> > > -- > 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. -- 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.
