Topic: ▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!KAWPOW!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂ - page 219. (Read 279744 times)
Crackfoo, you should really publish a stat/graph showing Nemo's daily profitability vs straight Zcash. I believe it's a great benchmark and would highlight how well the coin+algo switching is doing. A bit like an advanced version of Webbson's poolpicker, whacha think?
Crackfoo, can you please take a look into the equihash connection issues.... i just looked through my output file i spit to a text document the last 24 hours, i lost connection to equihash 61 times during mining with failed to reconnect attempts 3 times each, forcing my batch to switch to another algo to mine... i would really like to switch my other rigs back over to allow mining of equihash, since its one of the more profitable ones currently.. but the disconnects are brutal throughout the day...
hmq1725 reporting low hash rate again.
I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...
I just bumped the starting diff to 64 from 8.
Speaking of difficulty. Nicehash will not allow zpool as a pool due to low diff. Might be an opportunity for you.
What algo??? AFAIK NH doesn't offer hmq1725.
Oops, Scrypt. NH will not allow me to rent and point scrypt to zpool due to low diff
Seems ok now:
Received mining.set_difficulty... OK: difficulty=8192
Received mining.notify work... OK
Pool verification process is complete. Tested pool is compatible!
hmq1725 reporting low hash rate again.
I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...
I just bumped the starting diff to 64 from 8.
Speaking of difficulty. Nicehash will not allow zpool as a pool due to low diff. Might be an opportunity for you.
What algo??? AFAIK NH doesn't offer hmq1725.
Oops, Scrypt. NH will not allow me to rent and point scrypt to zpool due to low diff
Any idea what these VirtuaUnique coins that are getting mined in Nist5? They don't seem to show how many blocks are required for maturity.
Don't see it listed under the Nist5 pool, but seen them show up a few times now.
Don't see it listed under the Nist5 pool, but seen them show up a few times now.
Not all my coins are visible for a number of reasons. A couple being, maintaining profiability and testing new coins. Probably another 10 or so that are hidden. you still get your credits for them of course.
HI!! 
Looks as though NiceHash has changed the minimum difficulty for Qubit.
https://www.nicehash.com/?p=pool-operators
Looks as though NiceHash has changed the minimum difficulty for Qubit.
https://www.nicehash.com/?p=pool-operators
fixed
Any idea what these VirtuaUnique coins that are getting mined in Nist5? They don't seem to show how many blocks are required for maturity.
Don't see it listed under the Nist5 pool, but seen them show up a few times now.
Don't see it listed under the Nist5 pool, but seen them show up a few times now.
HI!!
Looks as though NiceHash has changed the minimum difficulty for Qubit.
https://www.nicehash.com/?p=pool-operators
Looks as though NiceHash has changed the minimum difficulty for Qubit.
https://www.nicehash.com/?p=pool-operators
i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect
https://farm5.staticflickr.com/4265/35529090375_5f8fe62ac8_z_d.jpg
https://farm5.staticflickr.com/4265/35529090375_5f8fe62ac8_z_d.jpg
Storx, I am getting similar issues - equihash either has disconnets or HIGH (90%) reject rate (stock settings 82% power NO OC on 6x1080tis). On my 2 card test rig I have no issues with it.
I think I will do the same, take it out of my multi-algo until it is resolved.
where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.
2) Last statement was confirmation of server side rejects not being factual - no need to reply (edited)
don't pay any attention to the graphs they are rubbish... just monitor the miner console..
Nemo
Nemo
I know this, i was just giving him the graph to give him an idea of when the issues were happening, not any numerical value to how many errors.. just a timeline compared to traffic spikes... good job on the miner btw, i tested it out lastnight.. but i found it locking up my rigs to often.. so i switched back the miner i have been using.. look forward to your future progress..
Do anny know how to setupp Yellowjacket 2.2 GH/s USB ASIC Miner (Nanofury) whit BFGMiner to work whit Zpool?
https://www.amazon.ca/Yellowjacket-2-2-ASIC-Miner-Nanofury/dp/B00I21R4HG
I have tryd sha256.mine.zpool.ca:3333 but BGFminer says "All the pools are dead".
Sorry for my bad english.
SINCERELY
Benny
https://www.amazon.ca/Yellowjacket-2-2-ASIC-Miner-Nanofury/dp/B00I21R4HG
I have tryd sha256.mine.zpool.ca:3333 but BGFminer says "All the pools are dead".
Sorry for my bad english.
SINCERELY
Benny
don't pay any attention to the graphs they are rubbish... just monitor the miner console..
Nemo
Nemo
i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect
Storx, I am getting similar issues - equihash either has disconnets or HIGH (90%) reject rate (stock settings 82% power NO OC on 6x1080tis). On my 2 card test rig I have no issues with it.
I think I will do the same, take it out of my multi-algo until it is resolved.
where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.
The miner is loosing connection to the server at random intervals and seems to reject reconnects for long periods of time. I can assure you its not my internet or miners, because its happening within seconds of one another on ALL my rigs and half are located at a different location on a completely different ISP service.
Just today monitoring my 1 rig i left on equihash.. i noticed that it seems to disconnect right around the peaks of the day when the miner count spikes high from everyone switching... and if you do manage to not get disconnected.. the miner will report a ton of errors for a few minutes tell things settle down.. its like a 50/50 on the disconnect vs error phase occurring..
hmq1725 reporting low hash rate again.
I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...
I just bumped the starting diff to 64 from 8.
Speaking of difficulty. Nicehash will not allow zpool as a pool due to low diff. Might be an opportunity for you.
What algo??? AFAIK NH doesn't offer hmq1725.
where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.
Rejects at pool
Share above target 0.0000 MSol/s 0.0000 MSol/s
Stale share 0.0000 MSol/s 0.0001 MSol/s
Duplicate share 0.0000 MSol/s 0.0000 MSol/s
Invalid nTime 0.0000 MSol/s 0.0000 MSol/s
Invalid worker 0.0000 MSol/s 0.0000 MSol/s
Other 0.0000 MSol/s 0.0000 MSol/s
a/some stale shares but nothing I'd be concerned about.
where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.
Rejects at pool
Share above target 0.0000 MSol/s 0.0000 MSol/s
Stale share 0.0000 MSol/s 0.0001 MSol/s
Duplicate share 0.0000 MSol/s 0.0000 MSol/s
Invalid nTime 0.0000 MSol/s 0.0000 MSol/s
Invalid worker 0.0000 MSol/s 0.0000 MSol/s
Other 0.0000 MSol/s 0.0000 MSol/s
i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect
Storx, I am getting similar issues - equihash either has disconnets or HIGH (90%) reject rate (stock settings 82% power NO OC on 6x1080tis). On my 2 card test rig I have no issues with it.
I think I will do the same, take it out of my multi-algo until it is resolved.
where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.
i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect
https://farm5.staticflickr.com/4265/35529090375_5f8fe62ac8_z_d.jpg
https://farm5.staticflickr.com/4265/35529090375_5f8fe62ac8_z_d.jpg
Storx, I am getting similar issues - equihash either has disconnets or HIGH (90%) reject rate (stock settings 82% power NO OC on 6x1080tis). On my 2 card test rig I have no issues with it.
I think I will do the same, take it out of my multi-algo until it is resolved.
hmq1725 reporting low hash rate again.
I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...
I just bumped the starting diff to 64 from 8.
Speaking of difficulty. Nicehash will not allow zpool as a pool due to low diff. Might be an opportunity for you.
hmq1725 reporting low hash rate again.
I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...
I just bumped the starting diff to 64 from 8.
Thanks. I think that helped, but will wait to see if it stays that way.
Jump to: