Issue #13103 has been updated by Josh Cooper. Status changed from Investigating to Closed
I have confirmed that the issue of 100% cpu utilization while polling socket.read has been fixed in ruby 1.9, so I am closing this. There is a separate issue about being able to specify the priority/nice level, which is #21241. ---------------------------------------- Bug #13103: CPU reached 100% during catalog run on puppet node https://projects.puppetlabs.com/issues/13103#change-93452 * Author: Collaboration TR * Status: Closed * Priority: Normal * Assignee: Josh Cooper * Category: windows * Target version: * Affected Puppet version: * 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
