So I implore you to check the share rate generation and pretty much ignore the reported hashrate when comparing notes. Remember that cgminer AND raper use virtually identical kernels so should hash at virtually identical rates.
Finally, the word is out. Now I don't need to post that long post I was telling about on BTC-e.com chat. Thanks developer, hopefully Graet will understand that he just didn't tweak his Reaper enough...
Back on-topic, thanks for the development. Although my results are lower with CGMiner than with Reaper, I like the program.
The reason why it is running slower... I have 2 6950's, one with 1536 shaders and one with 1408 shader. I set reaper to use 4*1536 = 6144 concurrency and when I do this with CGMiner and add some intensity (say 18, just like reaper), the 1536 will produce a good hashrate (the same as reaper), but the 1408 shader counting card will throttle itself somewhere between 80 and 100% load. It's worse with a higher intensity.
Is it possible to separate the concurrency per GPU? Can I simply enter 6144,5632 ? Maybe that will work around the problem. Reaper is showing 100% load on both cards with a combined hashing rate of 873.7KH/s, 1.2% stales on a slight overclock (30+MHz core on 1536-shader and 50+MHz core on 1408-shader). CGMiner maxes out at 840 because of this problem.
This weird load-thing was my only concern.
P.s. it's not the temperature... it would throttle all the way back to 0% if it is overheating.
P.p.s. you need an LTC addy. Think it would fill up pretty fast.