- From: Mike <
>
- To:
- Subject: [chef] Re: chef 10.12 slower?
- Date: Mon, 6 Aug 2012 16:19:35 -0400
Who built the packages? Are they installed with Opscode's Omnibus installer?
On Mon, Aug 6, 2012 at 4:15 PM, John Alberts
<
>
wrote:
>
Anyone else notice chef 10.12 release being significantly slow just on
>
startup compared to 10.10?
>
>
>
~]# time /opt/chef/bin/chef-client -h
>
Usage: /opt/chef/bin/chef-client (options)
>
-S, --server CHEFSERVERURL The chef server URL
>
-k, --client_key KEY_FILE Set the client key file location
>
-c, --config CONFIG The configuration file to use
>
-d, --daemonize Daemonize the process
>
-E, --environment ENVIRONMENT Set the Chef Environment on the node
>
-g, --group GROUP Group to set privilege to
>
-i, --interval SECONDS Run chef-client periodically, in
>
seconds
>
-j JSON_ATTRIBS, Load attributes from a JSON file or URL
>
--json-attributes
>
-l, --log_level LEVEL Set the log level (debug, info, warn,
>
error, fatal)
>
-L, --logfile LOGLOCATION Set the log file location, defaults to
>
STDOUT - recommended for daemonizing
>
-N, --node-name NODE_NAME The node name for this client
>
--once Cancel any interval or splay options,
>
run chef once and exit
>
-o RunlistItem,RunlistItem..., Replace current run list with specified
>
items
>
--override-runlist
>
-P, --pid PIDFILE Set the PID file location, defaults to
>
/tmp/chef-client.pid
>
-s, --splay SECONDS The splay time for running at
>
intervals, in seconds
>
-u, --user USER User to set privilege to
>
-K, --validation_key KEY_FILE Set the validation key file location,
>
used for registering new clients
>
-v, --version Show chef version
>
-h, --help Show this message
>
>
real 0m10.072s
>
user 0m9.919s
>
sys 0m0.175s
>
>
>
~]# rpm -qa | grep chef
>
chef-10.12.0-1.el6.x86_64
>
>
versus
>
>
>
~]# time /opt/opscode/bin/chef-client -h
>
Usage: /opt/opscode/bin/chef-client (options)
>
-S, --server CHEFSERVERURL The chef server URL
>
-k, --client_key KEY_FILE Set the client key file location
>
-c, --config CONFIG The configuration file to use
>
-d, --daemonize Daemonize the process
>
-E, --environment ENVIRONMENT Set the Chef Environment on the node
>
-g, --group GROUP Group to set privilege to
>
-i, --interval SECONDS Run chef-client periodically, in
>
seconds
>
-j JSON_ATTRIBS, Load attributes from a JSON file or URL
>
--json-attributes
>
-l, --log_level LEVEL Set the log level (debug, info, warn,
>
error, fatal)
>
-L, --logfile LOGLOCATION Set the log file location, defaults to
>
STDOUT - recommended for daemonizing
>
-N, --node-name NODE_NAME The node name for this client
>
--once Cancel any interval or splay options,
>
run chef once and exit
>
-override-runlist RunlistItem,RunlistItem...
>
Replace current run list with specified
>
items
>
-P, --pid PIDFILE Set the PID file location, defaults to
>
/tmp/chef-client.pid
>
-s, --splay SECONDS The splay time for running at
>
intervals, in seconds
>
-u, --user USER User to set privilege to
>
-K, --validation_key KEY_FILE Set the validation key file location,
>
used for registering new clients
>
-v, --version Show chef version
>
-h, --help Show this message
>
>
real 0m1.342s
>
user 0m1.188s
>
sys 0m0.140s
>
>
>
~]# rpm -qa | grep chef
>
chef-full-0.10.10-1
>
>
>
>
>
--
>
John Alberts
Archive powered by MHonArc 2.6.16.