Here's what I'm getting so far from 4x7970s.
--------------------------------------------------------------------------------
(5s):1491.8 (avg):1391.3 Kh/s | Q:157 A:16893 R:117 HW:0 E:10760% U:1276.5/m
TQ: 15 ST: 16 SS: 0 DW: 108 NB: 10 LW: 2508 GF: 0 RF: 0
Connected to http://lc.ozco.in:9332 with LP as user ckolivas.0
Block: 3481059ff985cf07dc7c223dba82c6c4... Started: [02:10:37]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 54.0C 5371RPM | 364.5/346.6Kh/s | A:4176 R:24 HW:0 U:315.54/m I:-3
GPU 1: 54.0C 5417RPM | 374.6/350.2Kh/s | A:4294 R:32 HW:0 U:324.46/m I:-3
GPU 2: 52.0C 5308RPM | 374.3/349.2Kh/s | A:4295 R:24 HW:0 U:324.54/m I:-3
GPU 3: 48.0C 5295RPM | 381.0/352.4Kh/s | A:4228 R:37 HW:0 U:319.47/m I:-3
--------------------------------------------------------------------------------
Note that you can increase the hashrate further, on both this and reaper BUT it starts generating garbage. I know people have claimed higher hashrates, but be wary of these claims and look at that successful share submission rate. My mining rig is really struggling behind the weak wifi it runs off when trying to submit 1300 shares per minute. I'll be tweaking the command line settings so they mean something more useful though since intensity of -3 will be rather confusing, so I'll change the scale for scrypt.
There are settings for which reaper does not return high quantities of stales at high aggressions with few stales, they were being posted up on BTC-e the other day. As I recall the thread concurrency used was something around 10240 (maybe slightly higher, but still around 10k).
edit: here they are, for ~450kh/s
worksize 256
aggression 13
threads_per_gpu 4
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 8192
and for 650kh/s
worksize 256
aggression 13
threads_per_gpu 5
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 10240
You must use the 12.6 drivers and the latest SDK to get these hash rates