somebodyspecial :
... Does cuda turn junk cpu's into photoshop/premiere editing kings? ...
From what I've seen with AE, I expect it depends on the nature of the work one is doing. The lesser cache
could hurt in some cases, but a more severe issue might be those cases where a particular plugin one is
using can't be accelerated with CUDA. When a friend of mine was trying various things out in AE, for
example, he found that the Shatter plugin really slowed things down, whereas an earlier section of the
animation (lots of raytracing) rendered very quickly with three 580s. Turned out the Shatter plugin code is
very old, doesn't get boosted by CUDA, and only runs on one CPU core.
Other than that, one might feel a degree of sluggishness if the system is having to cope with other tasks
at the same time, whether that's I/O loading from the main app being used, or some other task such as
a background virus check. Best to run such systems standalone so one doesn't have to install any
security stuff. The slower RAM support could be a limiting factor aswell.
Thus, using CUDA could I suppose make it a reasonable entry/budget system, but I reckon one would
quickly tire of the various likely limiting factors. Too many aspects of using a pro app don't benefit from
CUDA, eg. the main interface.
I've not yet tested AE CPU issues with a dual-core, but today I did compare to a stock-speed P55
system with an i7 875K (3.2GHz) an 16GB RAM @ 1333, using four GTX 580s for CUDA. For the simple
Blender/BMW and Creativecow/AE CUDA tests the difference compared to a 3930K/4.7 system with
64GB/2133 RAM was minimal, but for a much more intensive AE test (a Titan would do it in about 25
or 30 mins) the difference was a lot more significant, about 14% slower. I'll test with an i3 550 later.
Ian.
PS. Alas I can't comment specifically re Premiere/Photoshop (don't know much about them), but feel
free to PM me to discuss further.