[Devtools] CDK 2.4 and Minishift CDK uses lots of CPU

[Rafael Benevides]

Yes. From CDK 2.3 to CDK 2.4 It became practically unusable to deploy
helloworld-MSA on it, having both with 6GB of memory and 2 CPUs.

On Mon, Mar 27, 2017 at 2:24 PM, Burr Sutter <bsutter at redhat.com> wrote:

> I should also mention that OpenShift inside the CDK was eating more CPU
> from CDK 2.1 to 2.4 - not sure which version we saw it "rise".    Rafael
> has declared CDK 2.4 unusable for the Helloworld MSA demo because it uses
> so much CPU.
>
> Let's see if Rafael is paying attention :-)
>
>
>
> On Mon, Mar 27, 2017 at 2:20 PM, Burr Sutter <bsutter at redhat.com> wrote:
>
>>
>>
>> On Mon, Mar 27, 2017 at 10:02 AM, Praveen Kumar <prkumar at redhat.com>
>> wrote:
>>
>>> On Mon, Mar 27, 2017 at 7:21 PM, Burr Sutter <bsutter at redhat.com> wrote:
>>> >
>>> >
>>> > On Mon, Mar 27, 2017 at 9:05 AM, Lalatendu Mohanty <
>>> lmohanty at redhat.com>
>>> > wrote:
>>> >>
>>> >>
>>> >>
>>> >> On Mon, Mar 27, 2017 at 6:30 PM, Burr Sutter <bsutter at redhat.com>
>>> wrote:
>>> >>>
>>> >>> Rafael and I have noticed that CDK 2.2+ seems to use a bit more CPU.
>>> >>> With the Minishift CDK, it really puts load on the machine
>>> >>>
>>> >>> https://screencast.com/t/oMYhnG6JdQ
>>> >>>
>>> >>
>>> >> This is when the setup is idle or running an application or starting
>>> up?
>>> >>
>>> >
>>> > In this case, it was idle
>>> >
>>> > ./minishift_cdk --username blahblah --password hello --metrics true
>>> start
>>> >
>>> >
>>> > and now it won't respond to stop :-)
>>> >
>>> > ./minishift_cdk stop
>>> >
>>> > Stopping local OpenShift cluster...
>>> >
>>> > Unregistering machine
>>> >
>>> > Error stopping cluster:  Error unregistring the VM: ssh command error:
>>> >
>>> > command : sudo subscription-manager unregister
>>> >
>>> > err     : exit status 70
>>> >
>>> > output  : Remote server error. Please check the connection details, or
>>> see
>>> > /var/log/rhsm/rhsm.log for more information.
>>>
>>> Ah, looks like it hangs, it happen when you your laptop goes in sleep
>>> mode or you close it without stopping minishift VM. Now only thing I
>>> can think of that you should grub xhyve process and kill it then stop.
>>> When you try to start it again please make sure you use same start
>>> option which you provide at first run time.
>>>
>>>
>> That was it!
>>
>> Is this a bug we are tracking and trying to kill ?  :-)
>>
>>
>>
>>> # ps aux | grep xhyve
>>> # sudo kill -9 <xhyve_process_id>
>>> # ./minishift stop
>>>
>>> >
>>> >
>>> >
>>> >
>>> >>
>>> >> -Lala
>>> >>
>>> >>>
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> Devtools mailing list
>>> >>> Devtools at redhat.com
>>> >>> https://www.redhat.com/mailman/listinfo/devtools
>>> >>>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > Devtools mailing list
>>> > Devtools at redhat.com
>>> > https://www.redhat.com/mailman/listinfo/devtools
>>> >
>>>
>>>
>>>
>>> --
>>> Praveen Kumar
>>> https://fedoraproject.org/wiki/User:Kumarpraveen
>>>
>>
>>
>


-- 
*Rafael Benevides | Senior Product Manager*
Director of Developer Experience
Follow me at Twitter: @rafabene <https://twitter.com/rafabene>
M: +1-407-401-3555
Register today at https://developers.redhat.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20170327/90a2de02/attachment.htm>