Pages:
Author

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

jr. member
Activity: 30
Merit: 2
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?

ZM will report the power consumption of each GPU in 0.6.1

Nice to know that dstm is going to have new version, especially on watt power monitor, I wait for this for a while already.
jpl
member
Activity: 154
Merit: 11
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?

ZM will report the power consumption of each GPU in 0.6.1
Very nice feature :-).
Any hahsrate improvement is possible ?

Yeah.. that is cool.
I have a small lame request.. how about a beep noise when it fails?.. or pick the windows sound when it fails?   I usually would love to know when it fails, but I'm never looking at the screen.  I guess there is the email send on flypool.
sr. member
Activity: 810
Merit: 444
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?

ZM will report the power consumption of each GPU in 0.6.1
Very nice feature :-).
Any hahsrate improvement is possible ?
full member
Activity: 350
Merit: 126
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?

ZM will report the power consumption of each GPU in 0.6.1
full member
Activity: 350
Merit: 126
I had a crash this morning on Linux with DSTM Miner v0.6:

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

 Huh


Could you pls provide your startup configuration?
full member
Activity: 350
Merit: 126
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
full member
Activity: 350
Merit: 126
Suggestions are welcome.
How about socks5 proxy support?


This was already requested, zm will support socks5 in future versions most likely.
full member
Activity: 350
Merit: 126
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.
full member
Activity: 226
Merit: 100
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?
newbie
Activity: 11
Merit: 0
I had a crash this morning on Linux with DSTM Miner v0.6:

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

 Huh
newbie
Activity: 39
Merit: 0
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!
newbie
Activity: 10
Merit: 0
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.
newbie
Activity: 20
Merit: 0
Suggestions are welcome.
How about socks5 proxy support?
newbie
Activity: 1
Merit: 0
The program crashes when the graphics card driver hangs and reboots. This is very bad.  Huh
jpl
member
Activity: 154
Merit: 11
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. 
newbie
Activity: 16
Merit: 0
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.
full member
Activity: 350
Merit: 126
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.
full member
Activity: 350
Merit: 126
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'
full member
Activity: 350
Merit: 126
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.
sr. member
Activity: 826
Merit: 440
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...)
Pages:
Jump to: