But on the other hand a developer who works for 8 hours a day is going to cost about 22 dollars -- which isn't that much when you take his salary into account.
In other words: stop being cheap and start saving money.
OTOH, you can optimize your code to run on the bigger iron while you check it on the small one on your desk to see if the results are correct. Computers can make billions of miscalculations per second if the programmer is not watchful enough.
And 22 dollars an hour is really cheap.
That actually turned me off OpenCL at the time. Are there any black boxish GPU-accelerated FFT implementations? I'd like a drop-in replacement for FFTW.
I seem to recall needing to transfer the data to GPU memory and other things like that when I last used it, but that was prior to toolkit 2.0 IIRC.
I'll start with this and see how it goes.