Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 22. (Read 225062 times)

Hi, DSTM. What is this?
2018-03-25 6:04:44|   GPU0  62C  Sol/s: 311.1  Sol/W: 3.25  Avg: 313.7  I/s: 168.3  Sh: 1.06   0.99 78  +
2018-03-25 6:04:45|   GPU1  59C  Sol/s: 306.5  Sol/W: 3.53  Avg: 303.5  I/s: 162.7  Sh: 1.08   0.99 78  +
2018-03-25 6:04:46|   GPU3  63C  Sol/s: 293.2  Sol/W: 3.41  Avg: 291.7  I/s: 156.4  Sh: 1.09   0.99 78 
2018-03-25 6:04:47|   GPU2  62C  Sol/s: 328.0  Sol/W: 3.25  Avg: 322.8  I/s: 172.4  Sh: 1.24   1.00 78 
2018-03-25 6:04:49|   GPU4  63C  Sol/s: 293.9  Sol/W: 3.23  Avg: 300.7  I/s: 161.2  Sh: 1.17   0.99 85  ++
2018-03-25 6:04:49|   ========== Sol/s: 1532.7 Sol/W: 3.33  Avg: 1532.4 I/s: 821.1  Sh: 5.65   0.99 79
2018-03-25 6:05:04|   GPU0  62C  Sol/s: 313.1  Sol/W: 3.25  Avg: 313.7  I/s: 168.3  Sh: 1.06   0.99 78 
2018-03-25 6:05:05|   GPU1  59C  Sol/s: 305.4  Sol/W: 3.53  Avg: 303.5  I/s: 162.7  Sh: 1.08   0.99 78 
2018-03-25 6:05:06|   GPU3  63C  Sol/s: 293.2  Sol/W: 3.41  Avg: 291.7  I/s: 156.7  Sh: 1.09   0.99 78  ++
2018-03-25 6:05:07|   GPU2  62C  Sol/s: 329.5  Sol/W: 3.25  Avg: 322.8  I/s: 173.1  Sh: 1.24   1.00 78 
2018-03-25 6:05:09|   GPU4  63C  Sol/s: 296.3  Sol/W: 3.23  Avg: 300.7  I/s: 161.2  Sh: 1.17   0.99 85 
2018-03-25 6:05:09|   ========== Sol/s: 1537.5 Sol/W: 3.33  Avg: 1532.4 I/s: 822.0  Sh: 5.65   0.99 79
2018-03-25 6:05:29|   GPU0  57C  Sol/s: 225.7  Sol/W: 3.25  Avg: 313.6  I/s: 123.0  Sh: 1.07   0.99 78  ++
2018-03-25 6:05:29|   GPU3  54C  Sol/s: 199.1  Sol/W: 3.41  Avg: 291.7  I/s: 109.2  Sh: 1.09   0.99 78 
2018-03-25 6:05:29|   GPU1  54C  Sol/s: 219.8  Sol/W: 3.53  Avg: 303.5  I/s: 116.1  Sh: 1.08   0.99 78 
2018-03-25 6:05:30|   GPU2  56C  Sol/s: 211.4  Sol/W: 3.25  Avg: 322.7  I/s: 113.3  Sh: 1.24   1.00 78 
2018-03-25 6:05:34|   GPU4  58C  Sol/s: 166.1  Sol/W: 3.23  Avg: 300.6  I/s: 88.2   Sh: 1.17   0.99 85 
2018-03-25 6:05:34|   ========== Sol/s: 1022.2 Sol/W: 3.33  Avg: 1532.0 I/s: 549.7  Sh: 5.65   0.99 79
2018-03-25 6:05:50|   GPU0  55C  Sol/s: 46.4   Sol/W: 3.24  Avg: 313.4  I/s: 29.6   Sh: 1.07   0.99 78 
2018-03-25 6:05:50|   GPU3  49C  Sol/s: 56.2   Sol/W: 3.41  Avg: 291.5  I/s: 29.5   Sh: 1.09   0.99 78 
2018-03-25 6:05:50|   GPU2  54C  Sol/s: 48.4   Sol/W: 3.25  Avg: 322.5  I/s: 25.0   Sh: 1.24   1.00 78 
2018-03-25 6:05:50|   GPU1  51C  Sol/s: 56.4   Sol/W: 3.53  Avg: 303.3  I/s: 29.3   Sh: 1.08   0.99 78 
2018-03-25 6:05:56|   GPU4  56C  Sol/s: 48.6   Sol/W: 3.23  Avg: 300.3  I/s: 26.4   Sh: 1.17   0.99 85 
2018-03-25 6:05:56|   ========== Sol/s: 256.0  Sol/W: 3.33  Avg: 1531.0 I/s: 139.7  Sh: 5.64   0.99 79
2018-03-25 6:06:12|   GPU0  52C  Sol/s: 58.4   Sol/W: 3.24  Avg: 313.2  I/s: 33.4   Sh: 1.06   0.99 78 
2018-03-25 6:06:12|   GPU2  52C  Sol/s: 56.7   Sol/W: 3.25  Avg: 322.3  I/s: 33.6   Sh: 1.24   1.00 78 
2018-03-25 6:06:12|   GPU1  49C  Sol/s: 66.3   Sol/W: 3.53  Avg: 303.1  I/s: 38.0   Sh: 1.08   0.99 78 
2018-03-25 6:06:14|   GPU3  46C  Sol/s: 67.7   Sol/W: 3.41  Avg: 291.3  I/s: 37.9   Sh: 1.09   0.99 94  +
2018-03-25 6:06:29|   GPU4  55C  Sol/s: 55.5   Sol/W: 3.23  Avg: 300.1  I/s: 31.0   Sh: 1.17   0.99 85 
2018-03-25 6:06:29|   ========== Sol/s: 304.6  Sol/W: 3.33  Avg: 1530.0 I/s: 173.9  Sh: 5.64   0.99 82
And the miner works as nothing happens (at first time i saw a few hours of that work, now i have a daemon that controls hashrate and reboot farm).
And sol/w said that all is fine.

Thanks for the stats. Nice work.

Can you explain your concerns more deeply?

It's secure if your network is secure. The worst a bad actor could do (if your LAN is unsecured or they are already present on your network) is send invalid shares to your proxy. If that's a concern, then adding proxy-local authentication would address that (already on the list if important to others).

The described method of installation always installs the latest canonical version, so if people are following instructions, they will have the official version, not a modified version.

Without knowing your concerns more deeply, it's hard to answer. But maybe it's better to have this discussion via PM or on the announcement thread to avoid polluting dstm's thread here. https://bitcointalksearch.org/topic/ann-aiostratum-proxy-v11-fast-multi-coin-mining-proxy-for-1000s-of-rigs-3179895

Hi DSTM!

Tell me where and what should be entered in the file json-rpc.th to display the current amount of hashed? Here is the current file:

Request:
-->{"id":1, "method":"getstat"}

Response:
<--{
    "id": 1,
    "result": [{
        "gpu_id":            0,         // GPU CUDA id
        "gpu_name":          "string",  // GPU name
        "gpu_pci_bus_id":    0,         // PCI bus id
        "gpu_pci_device_id": 0,         // PCI device id
        "gpu_uuid":          "string"   // GPU UUID
        "temperature":       0,         // current GPU temperature
        "sol_ps":            0.00,      // current Sol/s
        "avg_sol_ps":        0.00,      // average Sol/s
        "sol_pw":            0.00,      // current Sol/s / Watt
        "avg_sol_pw":        0.00,      // average Sol/s / Watt
        "power_usage":       0.00,      // current power usage
        "avg_power_usage":   0.00,      // average power usage
        "accepted_shares":   0,         // total amount of accepted shares
        "rejected_shares":   0,         // total amount of rejected shares
        "latency":           0          // network latency
    }],

    "uptime":   0,                      // uptime in seconds
    "contime":  0,                      // connection time in seconds (gets reset on reconnect)
    "server":   "string",               // server name
    "port":     0000,                   // port
    "user":     "string",               // username
    "version":  "string",                // zm version
    "error":    null
}



What do you need to write and where?

Thanks... is it secure and not hackable?

logfile full error message?..  does it hit a max file size?

Simply put, it sits in the middle between your miner(s) and your pool(s), in an effort to consolidate multiple miners/rigs through a single connection to the pool. Your miners connect to to the proxy, and the proxy connects to the pool (just once, even for multiple miners), resulting in a single difficulty for all connected miners.

Without a proxy, your miner connects directly to a pool. There's nothing wrong with this, generally speaking - but with miner crashes/restarts due to overclocking or bugs, the miner has to reconnect to the pool. This can mean that your miner is seen by the pool as 'new' after reconnecting, which is generally considered a bad thing (you can lose out on shares/sharerate as you might be treated as a pool hopper). It's important to note that there are multiple factors involved, and over time pools are likely trying to get better at detecting pool hopping more precisely.

With a mining proxy sitting in the middle, the proxy maintains the connection to the pool on miner disconnect, the proxy keeps track of current difficulty and mining job, etc. When miners reconnect, they receive those same values - essentially picking up where they left off. The pool doesn't see any disconnects, and so any impact from pool-hopping isn't attributed to your account.

In the past, others have stated that a 20% improvement in sharerate/shares/reduction in stale/invalid shares have been achieved through the use of a proxy. I'm interested whether this still holds true, assuming that miners and pools have actually improved over the last couple of years, which may not be that true... 🤔

You can access current performance values via json-rpc - it reports both current and average values.
The idea behind the averages on the webui: you don't look at it all the time - so if you check it let's say once a day you really want to know how your systems performs on average - however this has the drawbacks you've mentioned. I think it makes sense to add current values to the webui.

This was already requested - it's on my todo list.

This is most likely the result of unstable memory due to overclocking.

There is no general issue to run a CPU miner in parallel, however the solution rate might decrease.

Nvidia has disabled reporting of power consumption for the 1050ti in it's drivers. You can try to downgrade your driver.

It's the target set by the pool, difficulty is misleading here.
ZM 0.6.1 will print the difficulty in square brackets.

The pool wasn't able to find the job for the submitted solution.
This could be a bug on pool side.
If this happens more often - pls report the pool you're on - I'll take a look at it.

Right, gpu 2 fails to respond to all kind of calls.
The '52, 67, 75, 78, 72, 94' numbers are there to help debugging, there is nothing wrong with them in your case.

If zm isn't able to parse the configuration file it reports the line number on which the error occurred. 
So 'zm.conf:8 invalid parameter' means there was an error on line 8. However your configuration file looks fine.

How exactly does a 'proxy' work?

I just announced new mining proxy software, see the BCT post here: https://bitcointalksearch.org/topic/ann-aiostratum-proxy-v11-fast-multi-coin-mining-proxy-for-1000s-of-rigs-3179895

Open source, no devfee, multi coin/algo, just aiming to help miners out. Building it has been a great learning experience in the mining technology ecosystem. I appreciate the feedback - happy mining. Spread the word!

quite new to the whole mining gig, started with claymore doing eth only but reading that ZEC is more suitable for Nvidia as the rig i got at the moment is nothing but 1060 6GB, would it be more worthwhile to do ZEC than ETH? i know there are a lot of considerations, no right or wrong answer to it, but want to see more user's opinions and decide.

With 1080Ti, I can going to 4,53 sol/W.
You have to down the power and you will stay at 640 sol/s, but with fewer watts.
Make you try...
This is my best result, no other GPU make better result.