Skip to content
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

Open
MagePsycho opened this issue Feb 25, 2024 · 8 comments
Open

warden env up is so slow [Apple Silicon M3] #753

MagePsycho opened this issue Feb 25, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@MagePsycho
Copy link

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

warden env up

It takes a hell lot of time and at the end, it gives the following message

! elasticsearch-hq The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

To Reproduce

use Apple silicon M3 and run the command

warden env up

Expected Behavior

Docker pull command should be faster

Additional context

No response

@MagePsycho MagePsycho added the bug Something isn't working label Feb 25, 2024
@MagePsycho MagePsycho changed the title warden env up is so slow warden env up is so slow [Apple Silicon M3] Feb 25, 2024
@navarr
Copy link
Member

navarr commented Feb 25, 2024

I don't have access to an M3 for testing.

I would recommend disabling ELASTICHQ by adding WARDEN_ELASTICHQ=0 to your .env

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 warden env config. Remember to censor any confidential info in the output

@MagePsycho
Copy link
Author

I will look over this and let you know more with the details you asked for. Let us keep it open.

@navarr
Copy link
Member

navarr commented Aug 6, 2024

@MagePsycho do you have any follow-up here?

@iranimij
Copy link

iranimij commented Aug 8, 2024

It's fixed for Us by just disabling it,
ARDEN_ELASTICHQ=0
@navarr

@bap14
Copy link
Member

bap14 commented Aug 8, 2024

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 WARDEN_ELASTICHQ=0 to my projects has just become a common practice for me now.

@sajidunnar
Copy link

@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

@bap14
Copy link
Member

bap14 commented Oct 3, 2024

@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?

@sajidunnar
Copy link

@bap14 Thanks for your response I have setup Memory Limit to 16Gb and CPU Limit to 12
Thanks

CleanShot 2024-10-04 at 12 17 00@2x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants