Prohashing Mining Pool Forums

CritterDog wrote:Cgminer SUMMARY 47m MHS AVG 108.19

5 SEC AVG MHS 104.41
BLOCKS FOUND 7
GETWORKS 428
ACCEPTED 515
REJECTED 3

Total share count on the pool matches cgminer almost exactly after about 1 hour

After 1 hour 23 min now the shares submitted no longer match.

My miner states it sent 907
Prohash only 639 Shares

Only 3 rejects
17 blocks found

Pool only showing 92MHS
Miner showing 108MHS

Debitcoin dropped hash rate down to 77MHS on pool but not on CGminer

And now I am stuck at low hashrate like I explained in first post.. The shares stopped matching after about 1 hour 20 mins.. THe pool shows now I only have 644

My miner says 1013 shares accepted so my hash now on pool is stuck low between 80-90MHS

Update on Cgminer report after 2 hours
SUMMARY 2h 04m 22s of Mining MHS AV 108.09 MHS // 5 sec 109.93MhS
Found Blocks 24
Getworks 1,112
Accepted 1,363
rejects 7

Prohash reports
90MHS avg
Accepted 665
Avg hash after 2 hours 94.7

d=8192
I will let it go you can take a look at it and tell me if I need to change d=

My Share count has gone down on Prohash from I saw it at 680 about 10mins ago now it shows 663?
Work start delay only .34 sec

Stuck below 90MHS going to reboot the miner now and see what it does.

Update on Reboot: Down already to 86MHS seems to me I am not getting enough shares.. Going to lower to d=4096 and reboot again

No Difference on 4096
Cryptographicanomally really took a hit down to 40MHS on that coin maybe it has to stabilize its only been on line 10 min
Does not like Borgcoin or Casinocoin

Thanks. This info will be very helpful in debugging. I'm writing some queries right now to try to figure this out, and I'll get back to you soon with more info.

CritterDog wrote:My Share count has gone down on Prohash from I saw it at 680 about 10mins ago now it shows 663?
Work start delay only .34 sec

Stuck below 90MHS going to reboot the miner now and see what it does.

This was an error, and I fixed the problem. It turns out that the "2 hr share count" was only reporting shares within the past one hour. While I don't think that this issue is the cause of the other problems, I fixed it and the changes will be available once shares have been recorded for two hours.

In addition to that bugfix, I made another change that will be more conservative with work restart times. The work restart times are now higher than they used to be, which will cause coins with longer block times to be chosen more frequently.

If you could try this again later, please let me know what you find. I think the result will be that you see dramatically increased hashrate. If you do, then I'd like to try finding a middle ground where profitability will be higher but hashrate is slightly lower.