edit
I notice a hashrate drop to below 6mh/s and rise back again with xI=65.
Drop to xI=64 (6274kh/s) and is not dropping anymore.(10kh/s or so)
Edit2
As u can see the Accepted shares are calculate fine in sgminer, but the above value isn't.
Is it hard to change the above value to the value sgminer is showing with "G".?
edit3
Still stable after 3 hours.
Restarted and see if the other algos also be stable...6.346kh/s
Sigh... every time I get close someone has to leap farther ahead.
Looks like you encountered the same thing I did with the x-65/x-64 threshold. I'm running x-68 since last night, averaging 5.96 Mhash/GPU across 4 290X's over 12 hours. Stable apart from a renter trying to load dead pools for a while, LOL. I get up to around 6.17 Mhash on one of the GPU's but they keep dropping off and don't hold consistently at the highest speeds. But I'm still at 1020/1350 on the clocks so that explains much of my shortfall, I'm sure.
On scrypt I had all 4 of my GPU's individually tuned to four different engine and memory speeds for the fastest possible stable speed. I'm going to try the latest builds and settings you and badman74 helpfully shared, and then see if I can push individual GPU's higher. Thanks again!
EDIT: Dumb question - I've never messed with voltage settings before as I didn't want to fry anything. But I see in bullus' profile that he has vddc set to 0. Does that mean "go with the default setting"? As I understand it the reference voltage on a 290X is 1.0 volt. So if I wanted to try cutting that by 10%, should I put "0.9" in the vddc line, or "-0.1"? Reading the docs would have me trying the former, but bullus' example makes me think the latter is right.
That's funny cause 1 renter told I was selling a 4.2mh/s rig but I have 9.8mh/s.(4x7950)
At the graph at betarigs u see fluctuating hashrates but can't see that at sgminer like i saw it with xI=65.(290x)
Average is still 9.6mh/s, a bit lower than normal, but no way 4.2mh/s. Is there a tweak for flat hashrates? Decreasing intensity?
gpu-vddc is set at 0 ,because I set it with msi afterburner for testing. At github guide u should set it like "1.000"
I don't know where he saw 4.2, especially with your average per 2 hours right where it should be. The thing about Betarigs is that the hashrate they show is just based on their readings of your rig's submitted shares. There's two things you can do, you could explain to the renter that the accepted shares will be higher if they direct the rig to a pool that's closer to your rig, or you could change no-submit-stale to false (or just delete that line). Doing that would mean that your rig would still submit stales but at least his pool will see a higher amount of total shares submitted (and that would mean a more accurate gauge of your hashrate). Another issue with betarigs is that I don't think most people are setting the difficulty properly, so there's going to be pretty wild variance on your hashrate.
I might just create a pre-build paragraph to message the renter as soon as they rent the rig to make sure that they understand all of this and to try to help them out as best I can with finding the right pool (I can test the latency to their pool and let them know if it'll be a factor for stales/rejects) and kinda guide them through setting the difficulty properly for the hashrate of the worker.
Show Posts
