Share accepted.
[GPU 0] T=-1C A=-1% sols=16.513
[GPU 1] T=-1C A=-1% sols=16.378
(ST/INV/DUP): 18x 0ch(0/0/0)
Haven't experimented too much with changing the clock speeds yet, I just used default settings from my ETH mining, so switching between the two coins is pretty much effortless. The pleasant surprise was this "test" rig was drawing ~290 watts at-the-wall while mining ETH and this has dropped to 199 watts mining ZCash. This suggests the ability to potentially push the clocks higher with this algorithm.
A little update.
I have been playing around a bit more, it crashed immediately (console windows closes) if I push the memory clocks much more. However, it loves the core clock increases. I got my core set at 1300 MHz now, or 50 MHz past default, and I am cranking along at:
Work received: height=1301 diff=8694.1578 latency=156ms
[GPU 0] T=-1C A=-1% sols=18.712
[GPU 1] T=-1C A=-1% sols=18.068
I also tried adjusting the worksize and threads a bit as well and it seemed to have a slight improvement moving the worksize down to 192 and increasing threads to 11264, but not enough difference to be definitive yet.
It seems memory bus/frequency is a far more important metric than clock-speed. Try cranking up the memory as high as you can, and downlclocking your cores.