crc: Executable 'crc' and whole user experience very slow on macOS
General information
- OS: macOS
- Hypervisor: hyperkit
- Did you run
crc setupbefore starting it (Yes/No)?: Yes (crc setup --vm-driver hyperkit)
CRC version
version: 1.0.0-rc.0+34371d3
OpenShift version: 4.2.0-0.nightly-2019-09-26-192831 (embedded in binary)
CRC status
CRC VM: Running
OpenShift: Running (v4.2.0-0.nightly-2019-09-26-192831)
Disk Usage: 13.92GB of 32.2GB (Inside the CRC VM)
Cache Usage: 11.71GB
Cache Directory: /Users/disposable/.crc/cache
CRC config
- cpus : 4
- memory : 24000
Host Operating System
ProductName: Mac OS X
ProductVersion: 10.15
BuildVersion: 19A583
Hardware
Processor: Quad-Core Intel Core i7 / 4 GHz
Memory: 32GB
Hyperkit Version (hyperkit -v)
hyperkit: v0.20190201-11-gc0dd46
Steps to reproduce
- execute crc config view
- or execute crc config set cpus 4
- or crc setup or crc oc-env or…
- any crc command
Expected
A more responsive crc command and user experience.
Actual
It takes nearly 17 seconds for the crc commands to start/finish
Sometimes the crc command freezes the whole system.
After the cluster has started the whole user experience is very slow and unresponsive. Many timeouts when talking to the api internally, slow pod creation…
I know it’s all in an early stage, so no blame, just to give you some feedback.
Logs
Please let me know when I can search my logs for more details.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 19 (10 by maintainers)
On Win10 (Behind proxy, firewall, Symantec Endpoint Protection) there are similar very long reaction times
With minikube however everything reacted quick and smoothely.