2. Did anybody try fitting the second drive into non-server version? According to iFixit teardown there should be enough room to do that.
And there's a spare port for it, the question is can you find the right kind of cable?
I'd be inclined to go for the quad i7 server myself, Aperture is CPU intensive and will happily max out both CPUs on my '09 mini, and you won't have to worry about finding the right cable.
FWIW on A2 (see my specs at bottom of post), from what I can see, Core Image (therefore the GPU) is used for "live adjustments" on the display, whereas CPU is for rendering the image.
When scrubbing adjustment bars back and forth, I notice a spike in GPU usage (Up to 60%)
When you are done and click on the
next photo, you will see the "rendering previews" circular indicator appear, and you'll observe your CPU bars rising (in my case maxing out).
GPU usage remains around 0% during this time.
Similarly huge GPU spikes
while dodging and burning, when you click save and return to Aperture's main interface you'll notice CPU spike to render the image, whilst GPU remains low, around 0%.
You can look for yourself:
/Developer/Applications/Graphics Tools/OpenGL Driver Monitor.app
2009 Mac Mini,
Aperture 2, Snow Leopard, FWIW.
This may or may not be of use to you - as I can't speak for A3, OpenCL, Lion etc, but this is my general observation.
I'd be interested to see what people running A3 on SL/Lion (with an OpenCL compatible GPU) achieve, specifically if a notable increase in GPU usage is observable in
scenarios other than "live" manipulation.