In addition to these data points, it’s good to know how long a simple
chef-client -v takes as well and a high-level assessment of average cpu
utilization (the metric typically reported by taskmgr) during the
chef-client -v execution interval.
Opscode has been watching performance on Windows, the most recent work
here was tracked by http://tickets.opscode.com/browse/CHEF-3485, where
upgrading the Windows Omnibus package from Ruby 1.9.2 to Ruby 1.9.3
reduced periods of high cpu utilization (and overall execution time) ~
30-50%. Most of this came from cpu time spent processing requires. More
details in the aforementioned ticket, along with other future
optimizations under consideration.
Thanks for sharing the data on what you’re seeing.
Software Development Engineer, Opscode, Inc.
From: Peter Norton <firstname.lastname@example.org:email@example.com>
Reply-To: "firstname.lastname@example.org:email@example.com" <firstname.lastname@example.org:email@example.com>
Date: Wednesday, March 20, 2013 12:31 PM
To: "firstname.lastname@example.org:email@example.com" <firstname.lastname@example.org:email@example.com>
Subject: [chef] Re: Chef is slow on windows
You can selectively remove some ohai plugins if you don’t need their data. The most common example for this that I’ve noticed on this list is removing the passwd plugin which gets a list of users from your naming service (AD, I’d guess): http://wiki.opscode.com/display/chef/Disabling+Ohai+Plugins. Basically something like crawling for users in your AD server could be the cause of your slowness, so you can try excluding passwd and see if it works for you and your cookbooks, and if it does, then problem solved. If not, try other plugins one-at-a-time until you have success.
On Wed, Mar 20, 2013 at 3:50 AM, Akshay Pratinav <firstname.lastname@example.org:email@example.com> wrote:
Hi Opscode / Chef Developers / Chef Users,
I have been using chef on windows and the speed of chef-client on windows is very slow because it takes more time to load OHAI data etc on windows platform.
Is there a way we can solve this problem because it is affecting the performance of the app on windows?
Is Opscode working on this to solve the problem if there is no good solution now and what is the timeline ?