Miner- Optiminer/Zcash GPU miner v1.7!

hm claymore is windows only
guess we have to set hope on silentarmy if this doesn’t get better

It’s extremely bizarre that they all crash at the same time. Maybe the dev is dynamically adjusting the fee?

For me they all ‘crashed’ with(local time) following messages.

2016-11-14 23:40:22,640 WARN [stratum] disconnecting
2016-11-14 23:40:22,640 INFO [stratum] Retrying connecting to eu1-zcash.flypool.org in 20 ms.
2016-11-14 23:40:22,642 INFO [GPU5] Waiting for work from pool.
2016-11-14 23:40:22,644 INFO [GPU0] Waiting for work from pool.

I am not sure it was crash (but at least mining stopeed) since rigs was immediatly rebooted by watchdog script.

The probable reason is that optiminer stops if it can’t mine devfee (eu1-zcash.flypool.org is used for mining devfee). Not really sure since I also use eu1-zcash.flypool.org.

Open source software should be competitive in a few days from now. My buddy eXtremal from BitcoinTalk is working on it and he’s an excellent programmer.

Care to share how your watchdog script works? I’m familiar w/the concept of a watchdog script. In this case, wouldn’t the miner still be running? So if you watched the miner process, it wouldn’t know that the process stalled, right?

Maybe you parse the output of the miner and monitor the last time a share was accepted, and after a certain time if a share wasn’t accepted you reboot?

Optiminer/Zcash Release 0.3.2

Changes

  • Improve stratum client stability.
  • Re-enable file logging though --log-file.
  • Fix bug in extranonce subscription.
  • Reduced dev fee.

Planned features for 0.4.0

  • Watchdog that quits the miner when a GPU stops producing solutions.
  • Json monitoring port

Sorry for the stratum connectivity problems of the last versions. I did not have time to test run the miner, it just finished last Friday and it was a rewrite from scratch. That’s why I released it marked as Beta. I hope the stability will improve quickly based on your feedback. Today, I could run the new version for a full 12h today on flypool and nicehash where it did not show a single crash or freeze and had >99.9% of shares accepted on both pool.

There was a question earlier how I test my miner. I have a couple of different GPUs to run it on. I do not have any large-scale mining rigs, I am a dev not a mining pool operator (my first attempt to build a 5-card mining rig failed quite miserably). This means, testing mostly happens ‘in the wild’ after releasing. For future releases I will tough try to partner with some miners enabling large-scale tests before new versions go to the wild.

Thanks & Happy mining!

5 Likes

You could redirect output of miner to file and check if file change time is too old or last {N} lines of this file does not contain ‘[GPU{M}] Share accepted’.

92KHs dev account ?

Are you overexaggerating a tad bit too much ?

He is not. It is the devfee address.

Interesting so ~1/16th of the network is on Optiminer

About one percent of the hash rate goes to the dev.

AMD Linux miners make up at least 16 percent of the hash rate.

download points to 3.1.1 version

~1/16th of the network is on Optiminer (~1.XXMHs)
~10-15% goes to the dev so roughly ~100Kh/s (97.1KH/s on the pool)

Yeah ~1% is roughly my calculation

1 Like

Thanks for reporting. Fixed!

1 Like

Wow, I’ve not been paying close attention to the network hash rate, it has gone up a lot within the last 48 hours. Seems like it’s about to go up even higher:

Coming soon from Claymore, “about 200H/s on stock Nano, 180H/s on stock 390X, 145-150 on stock RX480.”

It’s time for me to get up from sleep and compete. :wink:

1 Like

This is thanks to Optiminer and Claymore

Sorry can you just look over RX480 8G hangs after 1 minute?

0.3.2 seems working fine… :yum:

Cards:

RX 480 8GB ~ 140 sol/s bios ram timing mod
R9 290x 4GB ~ 160 sol/s
R9 380x 4 GB ~ 90 sol/s
R9 390 8GB ~ 150 sol/s
R9 390x 8GB ~ 166 sol/s

:slight_smile:

do you have any idea how to overclock on 16.04 with AMDGPU-PRO driver?

rx 480 8gb stock ~130 sol

Sol and Watt of RX470 4GB at 0.3.2, anyone?