Build times for various Java web apps here at Concursive (updated)
Posted by Matt Rajkowski on July 30, 2012, 3:00 PM EDT
Concursive generates web application archives (.war files) for their apps. These are done all over the place...
- Build servers which continually build and run tests on the apps
- Application servers which are used to checkout the source and customizations, and deploy the .war into production
- Developer machines which are used to code, debug locally and then commit the code for everyone else
While I was waiting for a few builds this past week I decided to see what the effect of various machine configurations had on build times. These tests were not isolated in any way. The machines tested were doing what they normally do and the results from Apache Ant were displayed.
| Machine | ConcourseSuite CRM | ConcourseConnect | Cores | Speed |
|---|---|---|---|---|
| 2008 Dev Machine | 7 minutes 12 seconds | 3 minutes 15 seconds | 2 | 2.4GHz |
| 2009 Web Server | 2 minutes 6 seconds | 1 minute 45 seconds | 2 | 2.13GHz |
| 2010 Web Server | 2 minutes 3 seconds | 40 seconds | 8 | 2.27GHz |
| 2011 Web Server | 1 minute 46 seconds | 41 seconds | 16 | 2.0GHz |
| 2012 Dev Machine | 55 seconds | 26 seconds | 4 | 2.6GHz |
These results are typical from what I see in the logs. CPU is not the only important factor... load, more memory and faster disk play a role.
How long does it take you to "ant package" the apps? and what is your computer/features?
August 14, 2012: Updated the table to show MacBook Pro w/Retina times.
