[chef] Re: Re: Re: Re: Why is knife --help so slow??

[Torben Knerr < >]

Or use bundler (Gemfile + 'bundle exec knife help') if you have a plain ruby install and not rvm

On Oct 10, 2013 6:39 AM, "DV" < "> > wrote:

Thanks guys, I'll give gemset a try.

On Wed, Oct 9, 2013 at 2:00 PM, JJ Asghar < " target="_blank"> > wrote:

I recently ran into this problem myself.  The way I got around it was
upgrading to ruby 2.0.0 via rvm and created a gem set specifically to
chef/knife stuff.  It worked great for me, maybe give that a shot?

Best Regards,
JJ Asghar
e: " target="_blank"> | c: 512.619.0722 | o: 512.977.5876

On 10/9/13 3:55 PM, "Noah Kantrowitz" < " target="_blank"> > wrote:

>It has to process every gem on the system looking for knife plugins. If
>you strace it, you'll see a crazy number of stats and similar calls.
>
>--Noah
>
>On Oct 9, 2013, at 1:53 PM, DV < " target="_blank"> > wrote:
>
>> Hey all,
>>
>> I have a bash_completion script that calls "knife --help" to get a list
>>of suggestions. The script works great, but each call costs about 2
>>seconds due to "knife --help" taking this long.
>>
>> Any ideas why it's so slow? It isn't doing anything, just outputting
>>help info. Should take under a millisecond, right?
>>
>> $ time knife node --help >/dev/null 2>&1
>>
>> real    0m0.878s
>> user    0m0.776s
>> sys     0m0.100s
>>
>> --
>> Best regards, Dmitriy V.
>

--
Best regards, Dmitriy V.