There's a bug for this (don't have the link but it was filed recently)...it's only omnibus and only on platforms where omnibus has the newer version of rubygems
Sorry about that. I forgot to mention these are omnibus installer
installations. Wow, what a difference then between the two projects, a
7.5x increase in just the initial startup time.
On Mon, Aug 6, 2012 at 3:23 PM, Bryan McLellan btm@loftninjas.org wrote:
Anyone else notice chef 10.12 release being significantly slow just on
startup compared to 10.10?
Most of the 10.12.0 packages were built with the new ruby omnibus
project whereas 0.10.10 was mostly the clojure omnibus project, so
there could be significant differences there.
On Mon, Aug 6, 2012 at 3:59 PM, Phil Dibowitz phil@ipom.com wrote:
There's a bug for this (don't have the link but it was filed
recently)...it's only omnibus and only on platforms where omnibus has the
newer version of rubygems
Sorry about that. I forgot to mention these are omnibus installer
installations. Wow, what a difference then between the two projects, a
7.5x increase in just the initial startup time.
On Mon, Aug 6, 2012 at 3:23 PM, Bryan McLellan btm@loftninjas.org
wrote:
Anyone else notice chef 10.12 release being significantly slow just on
startup compared to 10.10?
Most of the 10.12.0 packages were built with the new ruby omnibus
project whereas 0.10.10 was mostly the clojure omnibus project, so
there could be significant differences there.
Yes, I can verify this. I also confirmed it was Ruby 1.9.2 by switching
out to 1.9.3. For me it wasn't a big deal so I just decided to wait until
Ruby gets bumped..
On Mon, Aug 6, 2012 at 3:59 PM, Phil Dibowitz phil@ipom.com wrote:
There's a bug for this (don't have the link but it was filed
recently)...it's only omnibus and only on platforms where omnibus has the
newer version of rubygems
Sorry about that. I forgot to mention these are omnibus installer
installations. Wow, what a difference then between the two projects, a
7.5x increase in just the initial startup time.
On Mon, Aug 6, 2012 at 3:23 PM, Bryan McLellan btm@loftninjas.org
wrote:
Anyone else notice chef 10.12 release being significantly slow just
on
startup compared to 10.10?
Most of the 10.12.0 packages were built with the new ruby omnibus
project whereas 0.10.10 was mostly the clojure omnibus project, so
there could be significant differences there.
Yes, I can verify this. I also confirmed it was Ruby 1.9.2 by switching out
to 1.9.3. For me it wasn't a big deal so I just decided to wait until Ruby
gets bumped..
On Mon, Aug 6, 2012 at 3:59 PM, Phil Dibowitz phil@ipom.com wrote:
There's a bug for this (don't have the link but it was filed
recently)...it's only omnibus and only on platforms where omnibus has the
newer version of rubygems
Sorry about that. I forgot to mention these are omnibus installer
installations. Wow, what a difference then between the two projects, a
7.5x increase in just the initial startup time.
On Mon, Aug 6, 2012 at 3:23 PM, Bryan McLellan btm@loftninjas.org
wrote:
Anyone else notice chef 10.12 release being significantly slow just
on
startup compared to 10.10?
Most of the 10.12.0 packages were built with the new ruby omnibus
project whereas 0.10.10 was mostly the clojure omnibus project, so
there could be significant differences there.
I confirm that with ruby 1.9.2 (from Omnibus or not) chef-client launch
times are 20 times higher (from 20 to 30 seconds on a typical ubuntu 12.04
m1.small on EC2).
Solved by migrating to ruby 1.9.3 where needed, and I'll stay with Ruby
1.8.7 where I can (launch times usually under 2 seconds).
Yes, I can verify this. I also confirmed it was Ruby 1.9.2 by switching
out
to 1.9.3. For me it wasn't a big deal so I just decided to wait until
Ruby
gets bumped..
On Mon, Aug 6, 2012 at 3:59 PM, Phil Dibowitz phil@ipom.com wrote:
There's a bug for this (don't have the link but it was filed
recently)...it's only omnibus and only on platforms where omnibus has
the
newer version of rubygems
Sorry about that. I forgot to mention these are omnibus installer
installations. Wow, what a difference then between the two projects,
a
7.5x increase in just the initial startup time.
On Mon, Aug 6, 2012 at 3:23 PM, Bryan McLellan btm@loftninjas.org
wrote:
Anyone else notice chef 10.12 release being significantly slow
just
on
startup compared to 10.10?
Most of the 10.12.0 packages were built with the new ruby omnibus
project whereas 0.10.10 was mostly the clojure omnibus project, so
there could be significant differences there.
I confirm that with ruby 1.9.2 (from Omnibus or not) chef-client launch
times are 20 times higher (from 20 to 30 seconds on a typical ubuntu 12.04
m1.small on EC2).
Solved by migrating to ruby 1.9.3 where needed, and I'll stay with Ruby
1.8.7 where I can (launch times usually under 2 seconds).
Yes, I can verify this. I also confirmed it was Ruby 1.9.2 by
switching out
to 1.9.3. For me it wasn't a big deal so I just decided to wait until
Ruby
gets bumped..
On Mon, Aug 6, 2012 at 3:59 PM, Phil Dibowitz phil@ipom.com wrote:
There's a bug for this (don't have the link but it was filed
recently)...it's only omnibus and only on platforms where omnibus has
the
newer version of rubygems
Sorry about that. I forgot to mention these are omnibus installer
installations. Wow, what a difference then between the two
projects, a
7.5x increase in just the initial startup time.
On Mon, Aug 6, 2012 at 3:23 PM, Bryan McLellan btm@loftninjas.org
wrote:
Anyone else notice chef 10.12 release being significantly slow
just
on
startup compared to 10.10?
Most of the 10.12.0 packages were built with the new ruby omnibus
project whereas 0.10.10 was mostly the clojure omnibus project, so
there could be significant differences there.
It's not a particularly intuitive thing to search for - I found that ticket because I knew the topic precisely, and I had seen that ticket before :-).
I created a pull request that updates both Ruby and RubyGems to the latest current versions. This also relates to CHEF-2871, which was specific about updating to Ruby 1.9.3.
You may see some improvement by simply updating the RubyGems version on a system. You can do that with this:
% sudo /opt/chef/embedded/bin/gem update --system
To illustrate that this may positively affect the performance on its own, an isolated example (my 2 core, 8G Ubuntu 12.04 system):
% /opt/chef/embedded/bin/gem --version
1.8.12
% time chef-client --help
real 0m13.034s
user 0m11.881s
sys 0m0.408s
Wow, that did it. Updated from rubygems 1.8.12 to 1.8.24 and running
chef-client -h went from 10.1s to 1.6s!
Another data point: this speeds up even ruby 1.9.3 tremendously.
On a (rather old, Atom-based, slow server) chef-client -h went from 34s to 9s
FYI, the Chef 10.14.0 Omnibus release is planned to be built on Ruby
1.9.3-p194 and Rubygems 1.8.24. A release candidate should be
available on Monday.