-
Notifications
You must be signed in to change notification settings - Fork 47
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
Apple M1 processor homebrew install very slow compared to docker image #89
Comments
A docked image is a read to run virtual machine (basically), while installing from a package manager like homebrew actually involves compiling the app you are trying to run. If you have a fast enough internet connection, downloading an image will be faster than compiling… |
Possibly due to installing the x86_64 builds and hence running under Rosetta, whereas Docker pulls the arm64 image automatically? Elastic does provide aarch64 builds which you can install instead by changing x86_64 → aarch64 in the formula URLs, if you're interested in troubleshooting further. |
This change ensures that on ARM-based macs, the `aarch64` packages are used, leading to better performance, less resource utilization and better battery usage. Closes elastic#89
This change ensures that on ARM-based macs, the `aarch64` packages are used, leading to better performance, less resource utilization and better battery usage. Closes elastic#89
Using the elasticsearch docker image as explained in the official reference documentation the performance is great: https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html. It is comparable to a setup on my Linux laptop.
But, when installing elasticsearch with homebrew
brew install elasticsearch-full
, I've noticed it is several times slower. For example my Ruby on Rails test suite runs normally in 20 seconds, but requires 2 minutes now.Since I'm not very knowledgable in elasticsearch, I don't know how to debug this further. But, I assume there' a simple explanation for the slowdown.
Any ideas? Thanks in advance!
The text was updated successfully, but these errors were encountered: