-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
warden env up
is so slow [Apple Silicon M3]
#753
Comments
warden env up
is so slowwarden env up
is so slow [Apple Silicon M3]
I don't have access to an M3 for testing. I would recommend disabling ELASTICHQ by adding After that, would you be willing to do a short screen recording of you running up so I can see where the slowness is? Also, I'd appreciate it if you sent a copy of the output of |
I will look over this and let you know more with the details you asked for. Let us keep it open. |
@MagePsycho do you have any follow-up here? |
It's fixed for Us by just disabling it, |
Yeah, ElasticHQ doesn't have an arm build (at least not the tag we're using). All of the Warden flags also aren't documented anywhere as to how/when you can enable / disable automatically included services (like ElasticHQ). Adding the |
@MagePsycho I am on M2 Max , if I run 1 Magento and 2 wordpress docker then it takes all of my laptops ram and computer becomes slow , is it normal I have 32gb ram and instances are not heavy at all |
@sajidunnar Do you have Docker Desktop setup to allow consuming all your resources, or did you limit it to only say 50% memory and 50% CPUs? |
@bap14 Thanks for your response I have setup Memory Limit to 16Gb and CPU Limit to 12 |
Version of Warden
0.14.2
Operating System and Installation Method
MacOS 14.3
Describe the Bug
I use warden in Macbook Pro M3 Max (i.e. Apple Silicon M3). Whenever I start the new environment with the command
It takes a hell lot of time and at the end, it gives the following message
To Reproduce
use Apple silicon M3 and run the command
Expected Behavior
Docker pull command should be faster
Additional context
No response
The text was updated successfully, but these errors were encountered: