Our build is annoyingly slow. It’s a Java system built with Ant, and I’m running mine on Windows XP. Depending on the hardware, it can take between 5 to 15 minutes to complete.
Watching overall performance metrics on the machine, as well as correlating hardware differences with build times, indicates that the process is I/O bound. It also shows that the process does a lot more reading than writing.
However, I haven’t found a good way to determine which files are being read or written, and how many times. My suspicion is that with our many subprojects and subsequent invocations of the compiler, the build is re-reading the same commonly used libraries many times.
What are some profiling tools that will tell me what a given process is doing with which files? Free is nice, but not essential.
Using Process Monitor, as suggested by Jon Skeet, I was able to confirm my suspicion: almost all of the disk activity was reading and re-reading of libraries, with the JDK’s copies of ‘rt.jar’ and other libraries at the top of the list. I can’t make a RAM disk large enough to hold all the libraries I used, but mounting the ‘hottest’ libraries on a RAM disk cut build times by about 40%; clearly, Windows file system caching isn’t doing a good enough job, even though I’ve told Windows to optimize for that.
One interesting thing I noticed is that the typical ‘read’ operation on a JAR file is just a few dozen bytes; usually there are two or three of these, followed by a skip several kilobytes further on in the file. It appeared to be ill-suited to bulk reads.
I’m going to do more testing with all of my third-party libraries on a flash drive, and see what effect that has.
If you only need it for Windows, SysInternals Process Monitor should show you everything you need to know. You can select the process, then see each operation as it goes and get a summary of file operation as well.