Quote from: CNMOH on July 06, 2011, 08:00:53 PM

Quote from: teukon on July 06, 2011, 04:59:14 PM

Quote from: CNMOH on July 06, 2011, 03:56:40 PM

-w 128 gives me better results with my 5850.

Interesting. When I change to 128 my rate drops by a full 10 MH/s per 5850. Perhaps there are other settings which need to be changed in tandem to yield an improved rate.

Could you let me know your other settings? RAM speed, SDK version, Catalyst version, kernel type/version/patches, kernel parameters.

If your comments can improve my rate I'll tip in BTC.

For me, it's the opposite. I lose 10 MH/s if I set -w 256.

I'm actually using Phoenix, so my settings look a bit different:

Code:

start /DC:\Bitcoin\phoenix phoenix.exe -u http://******:******@eu.triplemining.com:8344 -k poclbm VECTORS BFI_INT AGGRESSION=11 DEVICE=0 WORKSIZE=128

Quote from: whopper on July 06, 2011, 07:43:48 PM

I'm running poclbm

Very interesting. On my system (980MHz core with 360MHz ram):

python phoenix.py -u http://:@:/ -a 1 -q 1 -k poclbm VECTORS BFI_INT AGGRESSION=11 WORKSIZE=256 DEVICE=1
401 MH/s (+/- 2 MH/s)

python phoenix.py -u http://:@:/ -a 1 -q 1 -k poclbm VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128 DEVICE=1

391 MH/s (+/- 2MH/s)

Perhaps this is something to do with RAM clock speed. I'll investigate.

Edit: Before getting to the RAM I noticed that this playing around with poclbm and AGGRESSION has frozen my card. This is the second time today! I really have to pull it back to 975 MHz unfortunately. I'll do my testing on my good core (still running well after 36 hours at 1020 MHz).