Issue #13103 has been updated by Pavel Drobushevich.
Josh Cooper wrote: > This may be more about how ruby implements blocking network IO on Windows. I > wouldn't be surprised if it used a busy wait loop to "select" on multiple > events, e.g. Ctrl-C. Is any update? Workaround, fix? We run puppet agent on windows nodes very often so CPU usage is incredible... ---------------------------------------- Bug #13103: CPU reached 100% during catalog run on puppet node https://projects.puppetlabs.com/issues/13103#change-65919 Author: Collaboration TR Status: Investigating Priority: Normal Assignee: Josh Cooper Category: windows Target version: Affected Puppet version: 2.7.12rc2 Keywords: windows, ftw Branch: After installing and ran command "puppet agent --test" on windows machine. I observed CPU utilization from task manager and found that The CPU usage reached 100% while connecting to puppet master to poll the catalog and dropped down when the catalog run is completed (about 10-30 seconds). I use puppet agent windows preview version 2.5 which the official version will be released this April. -- 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://projects.puppetlabs.com/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.
