Not a user of such behemoths myself, but in my organisation we've got a lot of GIS people and a few design/architect folks that work a lot with huge datasets, c

Not a user of such behemoths myself, but in my organisation we've got a lot of GIS people and a few design/architect folks that work a lot with huge datasets, complex models etc that require a fairly large amount of horsepower. It's funny the things that need a lot of beans to run; I was sitting with one of the GIS guys and he just clicked a button which then caused all 24 cores on his rig to flatline for about 4 minutes. The end result? A map of our city suddenly had a few boxes drawn over the top of it. As it turns out he was pulling in data from half a dozen sources to map out areas where there was government run housing that experienced higher than average levels of emergency services call outs. Apparently, in the past doing that manually would probably have taken several people about a week to do and wouldn't have been as accurate.