Recently I've seen people post about performance problems for the puppetd daemon. What I see is that the daemon uses resources even when it should be "asleep" waiting for the next scheduled run.
If you attach to a "sleeping" daemon, you'll see it's in a tight loop where it's constantly calling nanosleep() (on my Fedora linux workstation). I did some looking around, and I suspect it is a Ruby bug, related to this thread: http://www.ruby-forum.com/topic/164574 As far as I can tell, before any threads are used, ruby will sleep for long periods without constantly causing interrupts. But once ruby threads are used, even after the last thread exits, the timer is still set for a really short loop. Has anyone tried running puppetd with the patched version of Ruby? Does it improve the daemon's performance? It looks like it'll be included in 1.8.8, when that is released. -- Jonathan Billings <jonathan.billi...@umich.edu> The College of Language, Science, and the Arts LS&A IT - Research Systems and Support --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
