Issue #1781 has been updated by luke.
mgagne wrote: > > 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. It's not so much that it's a solution, as that it's what we can do right now. I've spent a ton of time profiling Puppet, looking for ways to make it faster, but I haven't always succeeded. We're always looking for help making it faster, and we'd be glad to make any changes toward better performance, but everything's a tradeoff. > 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. I've done this before, but maybe it's time to do it again. If you're willing to spend some time profiling, I'm willing to sew what I can do to trim the code you find is causing the slowdowns. > On the other hand, I think version 1.9 of Ruby would improve overall > performances. Will Puppet be compatible with Ruby 1.9? I don't actually know; I haven't had a chance to test it yet. I expect there will be at least some minor incompatibilities, but it shouldn't be anything significant from what I've seen. > 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. Clearly, and I'll always do what I can to help people improve Puppet. Let me know if I can help at all with the profiling. ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
