• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

New High End Build

jophde said:
1) Building the Android source itself requires 16gb of ram.

Thanks!
Click to expand...

No.. No it does not.. No idea where you picked up this false information but.. Yeah.. No.. It doesn't

Source: My computer. I can compile Android from source in about 35 minutes.
 
No.. No it does not.. No idea where you picked up this false information but.. Yeah.. No.. It doesn't

Source: My computer. I can compile Android from source in about 35 minutes.
Click to expand...

https://source.android.com/source/building.html

Sorry, I have only ever built inside a VM and in that case you do need 16 gb of ram or some amount of ram plus a swap file to make up the difference. I am sure you could do it on less. I imagine building make -j12 is going make use of quite a bit of ram. Yes, I know it probably won't use all 64Gb, or 32gb, but it will use quite a bit.

Regardless, firing up 24 (SDK 7 - 19 phone/tablet) headless emulators will actually make use of the ram when I am developing. I also need ram to run IntelliJ and build with Gradle. Gradle also does parallel builds of your app before loading it onto all the the emulators when running tests.

I believe setting up a development environment on this kind of hardware will give me a significant competitive advantage over most other professional Android Developers. Testing is fucking pain in the ass on most computers because the emulators are ARM images and dirt slow and the SDK doesn't even have real code to test against so real tests must be run on devices.

Setting up a 24 real devices is another option but it's slower and I find it to be ridiculous. This is how I deal fragmentation.
 
jophde said:
https://source.android.com/source/building.html

Sorry, I have only ever built inside a VM and in that case you do need 16 gb of ram or some amount of ram plus a swap file to make up the difference. I am sure you could do it on less. I imagine building make -j12 is going make use of quite a bit of ram. Yes, I know it probably won't use all 64Gb, or 32gb, but it will use quite a bit.

Regardless, firing up 24 (SDK 7 - 19 phone/tablet) headless emulators will actually make use of the ram when I am developing. I also need ram to run IntelliJ and build with Gradle. Gradle also does parallel builds of your app before loading it onto all the the emulators when running tests.

I believe setting up a development environment on this kind of hardware will give me a significant competitive advantage over most other professional Android Developers. Testing is fucking pain in the ass on most computers because the emulators are ARM images and dirt slow and the SDK doesn't even have real code to test against so real tests must be run on devices.

Setting up a 24 real devices is another option but it's slower and I find it to be ridiculous. This is how I deal fragmentation.
Click to expand...

Ahh gotcha. Didn't know you were exclusively building in a VM.. Makes sense you'd need 16GB of RAM then.. 8GB for the host 8GB for the VM..
 
You must log in or register to reply here.
Back
Top