Bitcoin Forum
May 23, 2019, 12:11:59 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 [151] 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 »
  Print  
Author Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows)  (Read 222130 times)
jpl
Member
**
Offline Offline

Activity: 154
Merit: 11


View Profile
March 24, 2018, 04:58:53 AM
 #3001

I just announced new mining proxy software, see the BCT post here: https://bitcointalk.org/index.php?topic=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!

How exactly does a 'proxy' work?

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... 🤔


Thanks... is it secure and not hackable?

1558613519
Hero Member
*
Offline Offline

Posts: 1558613519

View Profile Personal Message (Offline)

Ignore
1558613519
Reply with quote  #2

1558613519
Report to moderator
1558613519
Hero Member
*
Offline Offline

Posts: 1558613519

View Profile Personal Message (Offline)

Ignore
1558613519
Reply with quote  #2

1558613519
Report to moderator
1558613519
Hero Member
*
Offline Offline

Posts: 1558613519

View Profile Personal Message (Offline)

Ignore
1558613519
Reply with quote  #2

1558613519
Report to moderator
PLAY OVER 3000 GAMES
LIGHTNING FAST WITHDRAWALS
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1558613519
Hero Member
*
Offline Offline

Posts: 1558613519

View Profile Personal Message (Offline)

Ignore
1558613519
Reply with quote  #2

1558613519
Report to moderator
OlimpFil
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
March 24, 2018, 09:13:17 AM
 #3002

You can access current performance values via json-rpc - it reports both current and average values.

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?
wetblanket
Jr. Member
*
Offline Offline

Activity: 95
Merit: 2


View Profile
March 24, 2018, 03:46:27 PM
 #3003

I just announced new mining proxy software, see the BCT post here: https://bitcointalk.org/index.php?topic=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!

How exactly does a 'proxy' work?

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... 🤔


Thanks... is it secure and not hackable?


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://bitcointalk.org/index.php?topic=3179895

Improve mining pool share/hash rates with the aiostratum-proxy (https://bitcointalk.org/index.php?topic=3179895) stratum mining proxy.
ManeBjorn
Legendary
*
Offline Offline

Activity: 1288
Merit: 1004



View Profile
March 24, 2018, 11:36:04 PM
 #3004

Thanks for the stats. Nice work.

Hey ppl Smiley

I just finished testing the new v 0.6 with most of the Nvidia GTX 10xx cards, results below

GTX 1050 4GB Ti    = 180 Sol/s
GTX 1060 3GB       = 325 Sol/s
GTX 1060 6GB       = 345 Sol/s
GTX 1070 8GB       = 460 Sol/s
GTX 1070 11GB Ti  = 480 Sol/s
GTX 1080 11GB Ti  = 650 - 685 Sol/s

for more details check http://1stminingrig.com/new-dstms-zcash-cuda-miner-0-6-tested-reviewed/

SpecterHome
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
March 25, 2018, 03:36:43 AM
 #3005

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.
CarlOrff
Sr. Member
****
Online Online

Activity: 826
Merit: 439



View Profile
March 25, 2018, 06:37:59 AM
 #3006

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.
The miner is working (then it said you have 3.23 sol/s), but you have no share.
If you have no share, it is a possible issue from :
 - the miner
 - the pool
 - the network (switch, routeur, cables, firewall...)

Bitcoin + privacy respect = BitcoinZ (topic BitcoinZ)
The only decentralized crypto that complements Bitcoin on privacy.
You missed Bitcoin in 2009 ? Do not miss BitcoinZ in 2018 !
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
March 25, 2018, 08:48:36 AM
 #3007

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

Are you running out of disk space?
Remember zm always appends data to the logfile - even on restarts such that you never loose logfile data after restarts.
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
March 25, 2018, 08:49:10 AM
 #3008

You can access current performance values via json-rpc - it reports both current and average values.

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?



You have to send a json-rpc request in order to get the data. json-rpc.txt is not a configuration file - it describes the data format.
You can test json-rpc on unix systems with this command: 'echo "{\"id\":1, \"method\":\"getstat\"}\n" |nc 127.0.0.1 2222'
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
March 25, 2018, 08:50:05 AM
 #3009

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.

If your system is overclocked test if this also happens on default clock settings - an overclocked/unstable system behaves unpredictable.
You can also check if some other process starts consuming cpu - this might result in an reduced solution rate.
Sol/W uses average values - since this is the most accurate way to calculate it - so it takes some time till it converges.
DiggyDiggy
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
March 25, 2018, 09:27:28 AM
 #3010

I had 430sol/s on average with 1070 asus strix with EBWF miner. With this one I het around ~30sol/s more (for the total in range of 455-470 sol/s now).
So it seems good but the EBWF's way of the display was easier on the glance - temperatures sorted by the GPU number for example as I immediately new if something is fishy. If the first one had lower temp than the other as she is closes to the air filter with fresh air.
jpl
Member
**
Offline Offline

Activity: 154
Merit: 11


View Profile
March 26, 2018, 02:41:30 AM
 #3011

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

Are you running out of disk space?
Remember zm always appends data to the logfile - even on restarts such that you never loose logfile data after restarts.

Thanks for the reply.
43.8 gb used space
10.6 gb free

I think the logfile got up to 65 mb.. I deleted logfile, and tag from miner .. seems to be running fine. 
Andy911
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
March 26, 2018, 08:01:42 AM
 #3012

The program crashes when the graphics card driver hangs and reboots. This is very bad.  Huh
blackjec
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
March 26, 2018, 07:12:56 PM
 #3013

Suggestions are welcome.
How about socks5 proxy support?
kamak
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
March 26, 2018, 10:01:06 PM
 #3014

Miner Intensity?Huh?

Can this be applied in the bat file? : ie., --intensity=0:1 or --intensity 0:1 or --?Huh?

Example: zm --server ssl://us1.zhash.pro --user XXXXXXXXX --pass x --port 3060 --intensity 0:1 (for one gpu)

"--intensity " is an "unknown option" in the bat file.
Nvid
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
March 27, 2018, 11:23:57 AM
 #3015

Hi DSTM,

Can you please add --PEC option as on EWBF cuda miner.

--pec shows you gpu wat usage as well as sols per watt.


Thank you!
symbiosoft
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
March 27, 2018, 03:41:37 PM
 #3016

I had a crash this morning on Linux with DSTM Miner v0.6:

*** stack smashing detected ***: ./zmminer terminated

 Huh
akuci
Full Member
***
Offline Offline

Activity: 226
Merit: 100


View Profile
March 27, 2018, 04:06:33 PM
 #3017

Hi DSTM,

Can you please add --PEC option as on EWBF cuda miner.

--pec shows you gpu wat usage as well as sols per watt.


Thank you!
You already have sols per watt, but the power consumption in watts would be nice.
What do you think DSTM?
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
March 28, 2018, 06:24:54 AM
 #3018

I had 430sol/s on average with 1070 asus strix with EBWF miner. With this one I het around ~30sol/s more (for the total in range of 455-470 sol/s now).
So it seems good but the EBWF's way of the display was easier on the glance - temperatures sorted by the GPU number for example as I immediately new if something is fishy. If the first one had lower temp than the other as she is closes to the air filter with fresh air.

Sorting order will be preserved in the next version.
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
March 28, 2018, 06:25:35 AM
 #3019

Suggestions are welcome.
How about socks5 proxy support?


This was already requested, zm will support socks5 in future versions most likely.
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
March 28, 2018, 06:30:27 AM
 #3020

Miner Intensity?Huh?

Can this be applied in the bat file? : ie., --intensity=0:1 or --intensity 0:1 or --?Huh?

Example: zm --server ssl://us1.zhash.pro --user XXXXXXXXX --pass x --port 3060 --intensity 0:1 (for one gpu)

"--intensity " is an "unknown option" in the bat file.

Intensity is configurable only trough configuration files (--cfg-file) currently. Next version will also accept intensity via command line options.
You can always check the accepted command line options and their description by executing zm without parameters.
Remeber - intensity is used to reduce the GPU load - there is no reason to set it to 1
Pages: « 1 ... 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 [151] 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!