-
Notifications
You must be signed in to change notification settings - Fork 534
Review minimum hardware specs #1381
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
Comments
LOL none of my physical machines have that much RAM... |
I am building MXE on Google Cloud Platform using smallest possible VM instance (1 vCPU, 0.6 GB memory). I build using build-pkg. The platform provides a range of VMs. In future I want to build each commit/pull request on all supported distributions. We can speed up builds by splitting by target. |
1 vCPU, 0.6 GB memory machine failed while building gcc. Probably 0.6 GB is too low. |
build-pkg completed on machine with 6 vCores and 5.6 Gb RAM (min amount of RAM for machine with 6 vCores). Target: i686-w64-mingw32.static. Time of first pass: 8 hours. Disk usage: 20/60Gb. |
@starius, can you test the minimum RAM needed for 4 vCores since that's more common physically? |
Unfinished build using build-pkg on Jessie machine with 1 vCore and 2Gb RAM. Target x86_64-w64-mingw32.shared takes 15 hours to complete. |
@TimothyGu, there are following standard options: In addition, custom machine can be created. For 2 vcores, min memory is 1.8 Gb. For 4 vcores, min memory is 3.6 Gb. I am going to test builds on both of them without build-pkg. |
15 Gb of storage for one target is not sufficient. Rebuilding with 30 Gb. Output of
|
2 vcores with 1.8 Gb RAM failed on building pcl with wrror message "virtual memory exhausted: Cannot allocate memory"
|
4 vcores with 3,6 Gb - successful build of target i686-w64-mingw32.static without build-pkg.
Disk utilization: 14/30 Gb. |
http://mxe.cc/#requirements
It's very hard to quantify minimums, but I've found 8GB memory (with 12GB swap) and 60GB storage to be "safe" for Linux VMs. (Note that both swap and disk are on dynamically expandable storage).
What specs are workable for both VMs and physical hardware?
The text was updated successfully, but these errors were encountered: