Android dev rant:

>Fixing some code
>Compile code
>Take a walk, waiting for gradle to finish compiling
>Almost 10 mins, notice typo on code, while still running gradle
>Fixing some code
>Compile code
>Take a... Wait a minute

@busuu at first it compiles for +-1 min.
Then you add more library to gradle. Then you add more.
Then my project added with external jar library.
Then it gets so slow.

I never experienced this worse until recently. Also change the JVM compile size to 4GB from default 1.5GB

True. Gradle takes alot of time, but it also depends upon your system requirement. You need 8GB RAM in order to compile gradle faster. I recently tried AS 2.4 preview 7. They have improved both instant run and gradle compile time along with damn gradle exceptions, which are not even resolved by clearing cache or restarting AS 😂

@DevToast does it mean 8GB for the JVM alone? If so, well.. that's quite some RAM. I just hope AS get less random crash! 😂

@greenrobo haha no. That is for overall windows os. It allows AS to breathe properly 😜

@DevToast well, I put on my dev rig some beastly 16GB. So there should be plenty of room 🤣

@greenrobo yup there should be :)

I use emulator, Build and install takes ~3 seconds on 16 gb ddr4, 6700k, 512gb samsung 850 pro

@mariuskaunietis can you share the recipe for super speedy results? Are you using more than 10++ libraries on gradle?

@greenrobo don't have pc now. Basically, give tons of memory for gradle daemons. Clean builds take up to a minute. Also, installation to device takes time, on emulator - it's instant. By the way, some projects include 30+ dependancies: appcompat, rx, kotlin, retrofit...

@mariuskaunietis how many do you give gradle daemons space? Yes, I do also use emulators most of the time. Unless I have to do some test cases with GPS and cameras..

@greenrobo i think 4gb for each instance. Plus I have some beta/experimental features enabled