Monday, November 19, 2007
Posted on Monday, November 19, 2007 2:44:52 AM (Mountain Standard Time, UTC-07:00)  Comments [3] | 
Categories: Productivity

Now that we've moved on, the first task in setting up the new office was to order some workstations. Since I'm an avid reader of Scott Hanselman's blog, his Ultimate Developer Rig series immediately came to mind.

The timing could barely have been better - Scott worked with Jeff Atwood (CodingHorror.com) to build a rocking developer box. What they ended up with was a wicked fast, over clocked, nearly silent monster for less than $2000. You can read Scotts initial impressions here, but this is what stuck with me...

It's ridiculously fast. The word "obscene" comes to mind. It's working at least 80% of the speed of my thoughts (as opposed to 10-20% on my last PC.) I wait for little. Even opening a tab in IE7, once a chore that made me cry, happens instantly. -- Scott Hanselman

Sounds good to me. Moving on...

Since they built this rig over the summer, we were able to up the ante a little, and still come in just around the $2000 mark.

Here's a link to Scott's part list. We just changed a few things.

CPU: The Need for Speed

We initially decided to build out exactly the Hanselman box, but then I did a little looking, and found we could get 3.0Ghz Dual Core CPU's for the same price as 2.4Ghz  Quad Core CPUs.

Thus the debate what's better for ArcGIS Development: 4 cores running slower, or 2 cores running faster? I Googled for "quad core vs dual core" and the top result is Jeff Atwood weighing in on this question. Read his post, but suffice to say he does a lot of testing, and cites other studies, but the punch line is that in most cases, you will be better off with a faster dual-core CPU than an quad core.

As far as Visual Studio 2005 is concerned, Jeff notes that there is no difference between dual and quad cores (scroll down on this review @ xtreview.com)

Back in GIS Land, since ArcMap is not designed for multi-core systems, it's not going to benefit from extra cores - performance is going to be limited by the CPU speed. So if I'm mainly running Visual Studio and ArcMap, then a faster dual core CPU is likely the best bet. If I was to load up ArcSDE, SQL Server, ArcGIS Server, IIS, and Visual Studio on the same box, then I may see more bang out of the quad box, but we'll be getting servers to run the heavy hitting parts of that stack. Dual core it is.

More Monitors

Since we're starting from the ground up, we needed to get monitors. Two monitors is great, and really should be the minimum setup for any developer. The increase in productivity is enormous. How much better will 3 be? We'll find out! Since the price of pretty much every part had dropped since their build, we were able to get each developer a 22 inch wide screen to be flanked by two 19 inchers, all from Acer. The photo below shows 15 monitors lined up at our temporary location (Chris's living room)

monitors

Other than that, it's pretty much the Hanselman rig. Big props to Scott Hanselman and Jeff Atwood for sharing the details of the build - this makes it much easier for others to dive right in and build great systems.

Our Part List (NewEgg.com):

Total: $1945

Amazing what you can get these days. By building them our selves, we saved ~$1500 per workstation over similar boxes from Dell (see below).

dell-system

Monday, November 19, 2007 9:45:40 AM (Mountain Standard Time, UTC-07:00)
Ok, that all looks cool.. but what is your business line now?
Monday, November 19, 2007 7:47:08 PM (Mountain Standard Time, UTC-07:00)
Dave,

I'm still doing the same thing - just for another group. We'll have a press release in the next week or so, and we'll be working out how "public" my employer will be in my blog.

Cheers,

Dave
Thursday, November 22, 2007 5:45:36 AM (Mountain Standard Time, UTC-07:00)
Sounds pretty awesome, Dave - I am building a developer machine as well, at the moment. Did you look at Dave Peters' ESRI configuration/sizing spreadsheet while you were putting together specs for your machines?

How does your developer group work together - do you load everything up locally on the workstation, do you do server-based work, do you work with VMs and slices configured for various types of scenarios?

I seem to run across a mix of approaches and haven't yet been able to get any comparison, apples to apples, or pros/cons.

Best of luck in your new company!
Comments are closed.