[chef] Re: Right sizing Chef11 Server

[Jeff Blaine < >]

> I am wondering about any guidelines on 'right sizing' a Chef11 server.

One of the first things that comes to mind, having nothing else
to offer aside from "start finding the bottleneck", is reduction
of node data saved with every Chef run. That might help.

See: https://github.com/opscode/whitelist-node-attrs

"Allows you to provide a whitelist of node attributes to save on the 
server. All of the attributes are still available throughout the chef 
run, but only those specifically listed will be saved to the server."

Ohai's full output on the CentOS 6.4 box I just tested on
returns 28KB(!) of data, 99% of which I have never wanted
to query the server for yet. So you could find at least some
I/O gain by whitelisting most of it based on your needs. If
your needs change, change the whitelist.