As I explained there, I would delete the VM once done for the day (set of
days where you're working on a functionality).
Given the nature of minishift, and if caching is properly configured (which
by default is not), and the time it takes to create a new VM, I would
destroy every time you move locations, that means, you go to a conference,
day one, create a VM, use it, stop it. Day 2 start, use stop, day 3, last
day, start, use and delete.
I would recommend you to stop the vms, for which desktop integration will
help to remember, if your not going to use minishift.
Also, virtualbox reserves the memory and cpu you set, which means that if
you forget to stop it, it'll be used, all of it. Xhyve on the contrary,
just use what it needs and when it needs it.
Hope this helps.
Jorge
Any typo was my phone
El sáb., 20 oct. 2018 21:01, Burr Sutter <bsutter(a)redhat.com> escribió:
On Sat, Oct 20, 2018 at 1:56 PM Jorge Morales Pou <jmorales(a)redhat.com>
wrote:
> This is why I asked to have the UI integration, to which you replied that
> you look into the virtualbox ui for that. I guess you don't look into that
> UI that often 🤣
>
I do use the VB UI, read-only
> I think that the desktop integration will be the best option to prevent
> having long time running machines.
>
This is the workflow I typically advocate:
>
>
>
https://blog.openshift.com/care-and-feeding-of-minishift-development-envi...
>
Great blog.
I use profiles and the image caching (which you showed me in Barcelona).
And the core of my question is "how often do I use minishift delete"?
Every day? Every week?
>
>
> Jorge
>
> Any typo was my phone
>
> El sáb., 20 oct. 2018 19:36, Burr Sutter <bsutter(a)redhat.com> escribió:
>
>> This is unrelated to the "minshift won't start in Mexico" issue
:-)
>>
>> I use the pattern of
>> - create the VM
>> - setup my demos
>> - minishift stop
>> - close laptop
>> - travel
>> - open laptop
>> - minishift start
>>
>> and every now and then, I forget to minishift stop, just close the
>> laptop.
>>
>> and I do notice a "decay" after some number of days. Normally this
>> decay shows itself as too much CPU usage by the minishift VM (virtual
>> box). Basically Virtualbox consumes so much CPU that it makes the overall
>> laptop sluggish and even when I am just running slides :-)
>>
>> How many days do you think a minishift might survive this kind of
>> treatment? What do we test for?
>>
>>
>> _______________________________________________
>> Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
>> To unsubscribe send an email to minishift-leave(a)lists.minishift.io
>>
>