I just noticed, while "make maps"ing on a quad-core Xeon at work, that ufo2map does not seem to be CPU or IO bound! Even on this mega-machine
one ufo2maps is leaving about 75% CPU free. I wonder what is holding ufo2map up?
For those compiling slowly: If your CPU can take it, you can speed up the map compilation by using "make maps -j X", where X is the number of jobs you want to run in parallel. So, in the example above "-j 3" should triple the compilation speed while still leaving the machine responsive.