Ah! Then they're not the same thing. According to the nVidia Wikipedia entry the 8600 GTS has only 8 pixel shaders.
http://en.wikipedia.org/wiki/Comparison_of_NVIDIA_Graphics_Processing_Units
The equation is slightly different for the 8xxx. The 3 divisor is for the newer GTX cards but the older cards need a 4 divisor (as quoted in post #4). So, your 8600 GTS @ 708 MHz would be: 8 * 708 / 4 = 1416 ±10% = 1274-1558 RAC.
The low end of that is a
little over what you're getting but it assumes a dedicated rig running 24/7 with no other programs taking up video time. The 10% variance was added not to indicate a range for a specific card but as a fudge factor for the series because the cards don't scale 1:1 with a change in pixel shaders.
But like I said, it is a
very rough calculation. At the time I did that it was better then nothing at all since we had almost no real world data for a guide. Looking at your numbers it seems to hold up, more or less,
but I am curious about it being even that far off. Is yours a dedicated rig or is it your daily driver? It wouldn't take much usage per day to put it inside that range, albeit on the low side. BFG GTX 260OC2
28 * 630 / 3 = 5880 ±10% = 5292-6468 RAC for a
dedicated rig - that checks.
GTX 285
32 * 648 / 3 = 6912 ±10 = 6221-7603 RAC (and from the looks of things, probably toward the low side of that range).
One thing I've noted in all these RAC discussions (CUDA or not) is that no one seems to take into account the usage factor. If you're using your rig to play games 8 hours a week that's 5% of the time and, depending on the game and BOINC settings, may drop your expected RAC by the same amount. Even light browsing will take up some time, though very little compared to a high-end game. I ran into that issue one weekend while I was doing a lot of video converting from *.avi to *.mpg. I ran IDK 16-20 hours of conversions that weekend (an old Opty rig) and the RAC for that machine dropped over 10% for the week!
Took awhile for me to figure it out but that was the only change in usage I had ...