Skip to main content

AndroidStudio and a RAM Disk

Ok, my iMac is late 2012 and only has 8GB of RAM. I decided to see if it would be possible to speed up my development cycle, especially for running unit tests and the like but just as much for an improved build time as well.

After much fiddling in the dark and reading some great pages, I eventually came up with the following solution that works for me but bear this in mind:

Danger Will Robinson

RAM is volatile so everything you do is gone forever when you unmount it or shutdown so don't forget to copy your changes elsewhere. If you have Git integrated properly then get into the habit of committing frequently.

I have considered writing a small bash script to run `rsync` from a custom menu option  (and thus a shortcut key binding) or look into using the Apple Automator to transfer any changed files across to the hard drive.

Whatever... you have been warned!

Step one: Create the RAM disk, I do it like this:

diskutil erasevolume HFS+ "RAMBO" `hdiutil attach -nomount ram://4194304`

Once that is done, the next thing I do is check out my project (as I don't leave any changes uncommitted overnight just in case!) as a "new" one from source control into the RAM disk, that will make indexing a lot faster, and everything in general.

Step Two: Gradle configuration

To tell gradle where to shove it (!) during a build, you need to add this to your project build.gradle file:

allprojects {
    buildDir = "/Volumes/RAMBO/gradle-build/${rootProject.name}/${project.name}"    repositories {
        jcenter()
    }
}

And then do a clean, rebuild and run. For me at least the change in build times and overall feelings of fuzzy warmness have been well worth it.

All the best.

Comments

Popular posts from this blog

Prime Peace

I think prime numbers are the numerical expression of peace. Restful nodes in the vibration of everything. Prime factorisation has always struck me as something truly astounding and it is reassuring to know that awsesome minds are hard at work trying to solve the Riemann hypothesis right now. There are some truly wonderful professional and amateur (in the nicest sense of the word) explorations I have watched recently and the ones that moved me the most, in order of cool factor were: This guy,Carlos Paris, has put in some serious work with AutoCAD and made some interesting observations. I truly enjoyed watching all of his four videos. Awesome work Carlos. As an interested amateur I found his work and thoughts to be very compelling. I am sure the professionals would groan or moan but to me this video is most excellent and informative. Speaking of the professionals, this video is also very interesting to watch as it goes some way to visually explaining the Riemann hypothesis in

Handling multipart/form-data with NanoHTTPD

I am in the process of reviving an old project from 2014 that I never finished because of other work commitments. In that time, bitrot has set in, the Android API has moved on and all in all, the home-brewed HTTP server I wrote using SocketServer and the org.apache libraries had to go! I looked around, found a couple of contenders and after much time decided to go with NanoHTTPD because it is lean, small and fits in exactly two files. The main server is in one file `NanoHTTPD.java`and there is another file called `ServerRunner.java` which manages instances of running servers. The others The other project I looked at is this one:  https://github.com/koush/AndroidAsync which led me a merry dance and I just couldn't figure out how get the POST data I had uploaded. I spent a few days really digging at it with Wire Shark too to make sure the data was going up. It was. Whatever... I had used it via a gradle dependency entry but I dropped it and went back to NanoHTTPD. For m