Quick update- I did some more tests this weekend.
- tried Powertune +20, this did pretty much nothing for me (but I'm not ruling it out, it may be configuration dependent. Will experiment with this again later)
- tried --thread-concurrency 11200: Not really any improvement. I keep trying this because I read in a tutorial a few weeks ago that to find your optimal TC number, you should start your miner with no TC argument and then see what it defaults to (found in the file name of the BIN file that's generated). When I do this it always uses 22400. So- since I'm using -g 2 (two threads rather than one), it *should* be 11200 for me. But, apparently it's still not. (may try again later... or maybe tri 11199??)
- tried --thread-concurrency 8191 again: BAM! Hashrates jumped up. Now running a pretty stable 705,710,720,700 avg. hash rates across GPU's 0,1,2,3. Has been running stable for 24+ hrs now.
- 8191 required that I could no longer use the pre-generated 8192 BIN file that I mentioned in previous posts. Seems to have made little or no difference, which makes me wonder if it was really helping initially or not.
http://i.imgur.com/govhIrK.jpg?1Current arguments are:
-I 13 -g 2 -w 256 --lookup-gap 2 --thread-concurrency 8191,8191,8191,8191 --gpu-memclock 1500,1500,1500,1500 --gpu-engine 1065,1075,1085,1065 --auto-fan --temp-cutoff 90,90,90,90 --temp-overheat 85,85,85,85 --temp-target 72,72,72,72 --expiry 1 --scan-time 1 --queue 0
Up next, going to experiment with...
- Lowering the voltage via TRIXX to see if I'm dealing with an overheating and therefore throttling VRM issue.
- Ways to increase my WU/s and see if I'm actually getting my money's worth out of my hashrate (if hashrate is doing awesome but WU/s is low, what's the point??)
- Ways to reduce rejected shares (what's the point of having an awesome hashrate if the pool is rejecting your work...??)
Comments always welcome. Thanks for taking the journey with me!
