Issue #1781 has been updated by mgagne.
Hi, Thanks for your answer. luke wrote: > Those signals you're seeing are Ruby's relatively silly way of sleeping, so > it's perfectly normal, and there's no way I can do anything about that. Ok, the problem is probably somewhere else then. > If you're concerned about the performance between runs, you can run puppet > out of cron just as easily as the daemon. So turning a blind eye on a problem I find important would be the solution? You can certainly understand that this "solution" is just a patch, doesn't solve anything at all under the hood and is not acceptable. There is certainly slow Ruby's components being used by Puppet and a profiling would be one of the way to determine what is causing all this CPU usage while waiting and doing nothing. On the other hand, I think version 1.9 of Ruby would improve overall performances. Will Puppet be compatible with Ruby 1.9? Don't get me wrong, I like Puppet and what it can bring overall. However there is certainly room for improvements and I hope we can find a way to make it better. Thanks for your time. ---------------------------------------- Bug #1781: Slow execution http://projects.reductivelabs.com/issues/show/1781 Author: mgagne Status: Rejected Priority: Normal Assigned to: Category: plumbing Target version: Complexity: Unknown Affected version: 0.24.5 Keywords: Hi, We are currently evaluating Puppet to see if it could be used as part of our management system. I'm currently facing what I consider serious performance issues. In fact, Puppet seems to be very slow in general. Let me show you a first example: $ time puppet --version 0.24.5 real 0m0.718s user 0m0.576s sys 0m0.140s During that time, there is hundreds, if not thousands "rt_sigprocmask(SIG_BLOCK, NULL, [], 8)" calls being made. All this to show the version. Is it normal? If yes, why? Can it be improved? As for my second example, I installed Puppet with a basic manifest: the "sudo" example given in the tutorial. The file is synced to the node, great. However, the puppet client is constantly using about 3-4% of the CPU. Again, hundreds of "rt_sigprocmask()" calls per second are being made. Is it normal? I'm just wondering if there is any problem or if it's a "normal" behavior. To be honest, this is currently a show stopper for me as I'm not interested in running a tool which would just drain the CPU for no apparent reason. Here is some information about the environment: OS: Debian GNU/Linux lenny/sid Kernel: 2.6.26-1-amd64 Ruby: ruby 1.8.7 (2008-08-11 patchlevel 72) [x86_64-linux] Puppet: 0.24.5 Can you provide some help/hints about it? Any help will be appreciated. Thanks. ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
