Maybe there is an opportunity to increase performance on GDDR5X? (1080 and 1080TI) Due to prefetch and 64B data per memory access ?
Actually this is something that increases memory latency as far as I understand.
Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 126. (Read 224961 times)
October 30, 2017, 03:08:43 AM
Actually this is something that increases memory latency as far as I understand.
October 30, 2017, 03:04:41 AM
October 30, 2017, 02:48:23 AM
Maybe there is an opportunity to increase performance on GDDR5X? (1080 and 1080TI) Due to prefetch and 64B data per memory access ?
https://3dnews.ru/assets/external/illustrations/2016/01/22/927113/sm.micron_gddr5x.600.jpg
https://3dnews.ru/assets/external/illustrations/2016/01/22/927113/sm.micron_gddr5x.600.jpg
October 30, 2017, 02:42:35 AM
Code:
oct 30 00:37:46 miner4 zm[2999]: GPU2 49C Sol/s: 744.0 Sol/W: 3.40 Avg: 744.5 I/s: 399.1 Sh: 6.65 0.99 358 ++
oct 30 00:37:47 miner4 zm[2999]: GPU1 51C Sol/s: 735.9 Sol/W: 3.37 Avg: 739.8 I/s: 395.8 Sh: 5.70 1.00 356 ++
oct 30 00:37:48 miner4 zm[2999]: GPU0 55C Sol/s: 731.7 Sol/W: 3.34 Avg: 735.3 I/s: 393.6 Sh: 6.53 1.00 355
oct 30 00:37:50 miner4 zm[2999]: GPU4 57C Sol/s: 745.5 Sol/W: 3.38 Avg: 740.4 I/s: 396.1 Sh: 8.20 0.99 363 ++++
oct 30 00:37:50 miner4 zm[2999]: GPU3 58C Sol/s: 741.9 Sol/W: 3.37 Avg: 739.5 I/s: 395.8 Sh: 8.39 1.00 365
oct 30 00:37:53 miner4 zm[2999]: GPU5 57C Sol/s: 739.2 Sol/W: 3.37 Avg: 736.5 I/s: 394.0 Sh: 9.34 1.00 364 ++
oct 30 00:37:53 miner4 zm[2999]: ========= Sol/s: 4438.2 Sol/W: 3.37 Avg: 4435.9 I/s: 2374.4 Sh: 44.81 1.00 360
oct 30 00:38:06 miner4 zm[2999]: GPU2 49C Sol/s: 754.3 Sol/W: 3.40 Avg: 744.6 I/s: 399.3 Sh: 6.64 0.99 358 ++
oct 30 00:38:07 miner4 zm[2999]: GPU1 51C Sol/s: 739.9 Sol/W: 3.37 Avg: 739.8 I/s: 395.8 Sh: 5.74 1.00 356 +++
oct 30 00:38:07 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:08 miner4 zm[2999]: sslw slow network
oct 30 00:38:08 miner4 zm[2999]: GPU0 55C Sol/s: 731.3 Sol/W: 3.34 Avg: 735.2 I/s: 393.5 Sh: 6.49 1.00 355 +
oct 30 00:38:08 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:09 miner4 zm[2999]: sslw slow network
oct 30 00:38:09 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:10 miner4 zm[2999]: sslw slow network
oct 30 00:38:10 miner4 zm[2999]: GPU4 56C Sol/s: 731.4 Sol/W: 3.38 Avg: 740.2 I/s: 388.5 Sh: 8.25 0.99 363 ++++
oct 30 00:38:10 miner4 zm[2999]: GPU3 58C Sol/s: 745.9 Sol/W: 3.37 Avg: 739.6 I/s: 395.6 Sh: 8.40 1.00 365 +++
oct 30 00:38:11 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:11 miner4 zm[2999]: sslw slow network
oct 30 00:38:13 miner4 zm[2999]: GPU5 56C Sol/s: 704.6 Sol/W: 3.37 Avg: 736.1 I/s: 371.2 Sh: 9.45 1.00 364 ++++++
oct 30 00:38:13 miner4 zm[2999]: ========= Sol/s: 4407.3 Sol/W: 3.37 Avg: 4435.6 I/s: 2343.9 Sh: 44.96 1.00 360
oct 30 00:38:15 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:16 miner4 zm[2999]: sslw slow network
oct 30 00:38:18 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:18 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:18 miner4 zm[2999]: sslw slow network
oct 30 00:38:18 miner4 zm[2999]: sslw slow network
oct 30 00:38:20 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:21 miner4 zm[2999]: sslw slow network
oct 30 00:38:22 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:22 miner4 zm[2999]: sslw slow network
oct 30 00:38:26 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:26 miner4 zm[2999]: GPU2 49C Sol/s: 747.6 Sol/W: 3.40 Avg: 744.7 I/s: 399.2 Sh: 6.70 0.99 358 ++++
oct 30 00:38:27 miner4 zm[2999]: sslw slow network
oct 30 00:38:27 miner4 zm[2999]: GPU1 51C Sol/s: 742.8 Sol/W: 3.37 Avg: 739.8 I/s: 395.7 Sh: 5.85 1.00 356 +++++
oct 30 00:38:28 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:28 miner4 zm[2999]: GPU0 55C Sol/s: 731.2 Sol/W: 3.34 Avg: 735.2 I/s: 393.9 Sh: 6.48 1.00 355 ++
oct 30 00:38:29 miner4 zm[2999]: sslw slow network
oct 30 00:38:29 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:30 miner4 zm[2999]: sslw slow network
oct 30 00:38:30 miner4 zm[2999]: GPU4 56C Sol/s: 660.1 Sol/W: 3.38 Avg: 739.3 I/s: 358.3 Sh: 8.33 0.99 363 +++++
oct 30 00:38:30 miner4 zm[2999]: GPU3 58C Sol/s: 746.8 Sol/W: 3.37 Avg: 739.7 I/s: 395.6 Sh: 8.30 1.00 365
oct 30 00:38:33 miner4 zm[2999]: GPU5 56C Sol/s: 715.8 Sol/W: 3.37 Avg: 735.9 I/s: 378.5 Sh: 9.41 1.00 364 ++
oct 30 00:38:33 miner4 zm[2999]: ========= Sol/s: 4344.2 Sol/W: 3.37 Avg: 4434.5 I/s: 2321.2 Sh: 45.07 1.00 360
oct 30 00:38:33 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:33 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:33 miner4 zm[2999]: sslw slow network
oct 30 00:38:33 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:34 miner4 zm[2999]: sslw slow network
oct 30 00:38:34 miner4 zm[2999]: sslw slow network
oct 30 00:38:36 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:37 miner4 zm[2999]: sslw slow network
oct 30 00:38:37 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:37 miner4 zm[2999]: sslw slow network
oct 30 00:38:38 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:38 miner4 zm[2999]: sslw slow network
oct 30 00:38:39 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:39 miner4 zm[2999]: sslw slow network
oct 30 00:38:41 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:41 miner4 zm[2999]: sslw slow network
oct 30 00:38:45 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:45 miner4 zm[2999]: sslw slow network
oct 30 00:38:46 miner4 zm[2999]: GPU2 49C Sol/s: 747.2 Sol/W: 3.40 Avg: 744.7 I/s: 399.1 Sh: 6.70 0.99 358 ++
oct 30 00:38:47 miner4 zm[2999]: GPU1 51C Sol/s: 717.5 Sol/W: 3.37 Avg: 739.6 I/s: 380.0 Sh: 5.85 1.00 356 ++
oct 30 00:38:48 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:48 miner4 zm[2999]: GPU0 54C Sol/s: 741.4 Sol/W: 3.34 Avg: 735.2 I/s: 393.5 Sh: 6.40 1.00 355
oct 30 00:38:49 miner4 zm[2999]: sslw slow network
oct 30 00:38:50 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:50 miner4 zm[2999]: sslw slow network
oct 30 00:38:50 miner4 zm[2999]: GPU4 55C Sol/s: 663.9 Sol/W: 3.38 Avg: 738.3 I/s: 357.3 Sh: 8.41 0.99 363 +++++
oct 30 00:38:51 miner4 zm[2999]: GPU3 58C Sol/s: 732.8 Sol/W: 3.37 Avg: 739.6 I/s: 395.6 Sh: 8.23 1.00 365 +
oct 30 00:38:53 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:53 miner4 zm[2999]: GPU5 56C Sol/s: 680.2 Sol/W: 3.36 Avg: 735.2 I/s: 364.0 Sh: 9.44 1.00 364 ++++
oct 30 00:38:53 miner4 zm[2999]: ========= Sol/s: 4283.1 Sol/W: 3.37 Avg: 4432.6 I/s: 2289.6 Sh: 45.04 1.00 360
oct 30 00:38:53 miner4 zm[2999]: sslw slow network
oct 30 00:38:55 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:55 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:56 miner4 zm[2999]: sslw slow network
oct 30 00:38:56 miner4 zm[2999]: sslw slow network
oct 30 00:38:57 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:57 miner4 zm[2999]: sslw slow network
oct 30 00:38:58 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:38:59 miner4 zm[2999]: sslw slow network
oct 30 00:39:01 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:01 miner4 zm[2999]: sslw slow network
oct 30 00:39:06 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:06 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:06 miner4 zm[2999]: sslw slow network
oct 30 00:39:06 miner4 zm[2999]: sslw slow network
oct 30 00:39:06 miner4 zm[2999]: GPU2 48C Sol/s: 699.3 Sol/W: 3.40 Avg: 744.2 I/s: 375.2 Sh: 6.72 0.99 358 +++
oct 30 00:39:07 miner4 zm[2999]: GPU1 51C Sol/s: 706.9 Sol/W: 3.37 Avg: 739.2 I/s: 380.4 Sh: 5.86 1.00 356 ++
oct 30 00:39:08 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:08 miner4 zm[2999]: sslw slow network
oct 30 00:39:08 miner4 zm[2999]: GPU0 55C Sol/s: 733.6 Sol/W: 3.34 Avg: 735.2 I/s: 393.1 Sh: 6.33 1.00 355
oct 30 00:39:08 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:09 miner4 zm[2999]: sslw slow network
oct 30 00:39:10 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:10 miner4 zm[2999]: sslw slow network
oct 30 00:39:10 miner4 zm[2999]: GPU4 54C Sol/s: 682.7 Sol/W: 3.38 Avg: 737.7 I/s: 365.5 Sh: 8.46 0.99 363 ++++
oct 30 00:39:11 miner4 zm[2999]: GPU3 58C Sol/s: 742.8 Sol/W: 3.37 Avg: 739.6 I/s: 395.5 Sh: 8.24 1.00 365 +++
oct 30 00:39:13 miner4 zm[2999]: GPU5 56C Sol/s: 705.8 Sol/W: 3.37 Avg: 734.8 I/s: 380.0 Sh: 9.40 1.00 364 ++
oct 30 00:39:13 miner4 zm[2999]: ========= Sol/s: 4271.1 Sol/W: 3.37 Avg: 4430.7 I/s: 2289.8 Sh: 45.00 1.00 360
oct 30 00:39:19 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:19 miner4 zm[2999]: sslw slow network
oct 30 00:39:23 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:24 miner4 zm[2999]: sslw slow network
oct 30 00:39:26 miner4 zm[2999]: GPU2 49C Sol/s: 729.1 Sol/W: 3.40 Avg: 744.0 I/s: 391.4 Sh: 6.68 0.99 358 +
oct 30 00:39:27 miner4 zm[2999]: GPU1 51C Sol/s: 704.9 Sol/W: 3.37 Avg: 738.8 I/s: 380.3 Sh: 5.86 1.00 356 ++
oct 30 00:39:28 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:28 miner4 zm[2999]: sslw slow network
oct 30 00:39:28 miner4 zm[2999]: GPU0 54C Sol/s: 740.1 Sol/W: 3.34 Avg: 735.3 I/s: 393.8 Sh: 6.29 1.00 355 +
oct 30 00:39:30 miner4 zm[2999]: GPU4 56C Sol/s: 743.0 Sol/W: 3.38 Avg: 737.7 I/s: 396.4 Sh: 8.36 0.99 363
oct 30 00:39:31 miner4 zm[2999]: GPU3 58C Sol/s: 737.2 Sol/W: 3.37 Avg: 739.6 I/s: 395.7 Sh: 8.21 1.00 365 ++
oct 30 00:39:33 miner4 zm[2999]: GPU5 56C Sol/s: 718.4 Sol/W: 3.37 Avg: 734.6 I/s: 386.5 Sh: 9.32 1.00 364 +
oct 30 00:39:33 miner4 zm[2999]: ========= Sol/s: 4372.8 Sol/W: 3.37 Avg: 4430.0 I/s: 2344.3 Sh: 44.71 1.00 360
oct 30 00:39:35 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:35 miner4 zm[2999]: sslw slow network
oct 30 00:39:36 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:36 miner4 zm[2999]: sslw slow network
oct 30 00:39:39 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:39 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:39 miner4 zm[2999]: sslw slow network
oct 30 00:39:40 miner4 zm[2999]: sslw slow network
oct 30 00:39:41 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:42 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:42 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:42 miner4 zm[2999]: sslw slow network
oct 30 00:39:42 miner4 zm[2999]: sslw slow network
oct 30 00:39:42 miner4 zm[2999]: sslw slow network
oct 30 00:39:45 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:45 miner4 zm[2999]: sslw slow network
oct 30 00:39:46 miner4 zm[2999]: GPU2 49C Sol/s: 711.1 Sol/W: 3.40 Avg: 743.6 I/s: 383.6 Sh: 6.67 0.99 358 ++
oct 30 00:39:47 miner4 zm[2999]: GPU1 51C Sol/s: 742.1 Sol/W: 3.36 Avg: 738.8 I/s: 395.9 Sh: 5.79 1.00 356
oct 30 00:39:47 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:48 miner4 zm[2999]: sslw slow network
oct 30 00:39:49 miner4 zm[2999]: GPU0 54C Sol/s: 729.1 Sol/W: 3.34 Avg: 735.2 I/s: 393.6 Sh: 6.21 1.00 355
oct 30 00:39:49 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:50 miner4 zm[2999]: sslw slow network
oct 30 00:39:50 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:50 miner4 zm[2999]: sslw slow network
oct 30 00:39:50 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:51 miner4 zm[2999]: GPU3 58C Sol/s: 745.3 Sol/W: 3.37 Avg: 739.7 I/s: 395.6 Sh: 8.12 1.00 365
oct 30 00:39:51 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:51 miner4 zm[2999]: sslw slow network
oct 30 00:39:51 miner4 zm[2999]: GPU4 54C Sol/s: 706.3 Sol/W: 3.38 Avg: 737.4 I/s: 372.9 Sh: 8.40 0.99 363 ++++
oct 30 00:39:51 miner4 zm[2999]: sslw slow network
oct 30 00:39:51 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:52 miner4 zm[2999]: sslw slow network
oct 30 00:39:53 miner4 zm[2999]: GPU5 55C Sol/s: 629.3 Sol/W: 3.36 Avg: 733.4 I/s: 340.5 Sh: 9.46 1.00 364 +++++++
oct 30 00:39:53 miner4 zm[2999]: ========= Sol/s: 4263.2 Sol/W: 3.37 Avg: 4428.0 I/s: 2282.2 Sh: 44.65 1.00 360
oct 30 00:39:53 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:53 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:54 miner4 zm[2999]: sslw slow network
oct 30 00:39:54 miner4 zm[2999]: sslw slow network
oct 30 00:39:56 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:39:56 miner4 zm[2999]: sslw slow network
oct 30 00:40:00 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:40:00 miner4 zm[2999]: sslw slow network
oct 30 00:40:00 miner4 zm[2999]: sslw: SSL_ERROR_WANT_WRITE
oct 30 00:40:01 miner4 zm[2999]: sslw slow network
October 30, 2017, 01:48:45 AM
Hi
I'm still testing 0.5.3 on linux (14.04 LTS) driver 384, 1080Ti
so far 2-3% improvement over EWBF (with 1% fee, here is 2%)
CPU load is higher but not killer.
also testing on one of the 6x 1080s (driver 380), so far i haven't seen any difference in production at the pool.
the miner reports locally 3-4% more, but at the pool seems about the same.
will keep testing..
I'm still testing 0.5.3 on linux (14.04 LTS) driver 384, 1080Ti
so far 2-3% improvement over EWBF (with 1% fee, here is 2%)
CPU load is higher but not killer.
also testing on one of the 6x 1080s (driver 380), so far i haven't seen any difference in production at the pool.
the miner reports locally 3-4% more, but at the pool seems about the same.
will keep testing..
Quote
BTW: dstm, if you decide to add colors to the output, please put a switch that allow us to DISABLE it,
because in my case, i run a lot of scripting to read the real time data of the miner, and send it to a
webpage and to the LCD display of the miner, and dealing with colors is a pain in the ass
indkt.
because in my case, i run a lot of scripting to read the real time data of the miner, and send it to a
webpage and to the LCD display of the miner, and dealing with colors is a pain in the ass
indkt.
That's exactly the reason why I haven't put them in - also people might have different terminal background colors which makes colored output hard to read.
October 30, 2017, 01:45:53 AM
Can someone please tell me how to set the rig to mine with specific cards with this miner?
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
Is it really that hard to read a readme file?
Guess not...
Thanks (for being a dick)...I read the read me, I missed it before.
Is the dev command working for anyone else on 5.3? I tried it and it keeps crashing.
0.5.3 has a bug in device selection, this is fixed in the development branch, 0.5.2 works fine.
October 29, 2017, 10:56:11 PM
@dstm: pool closes connection (pool sexy), zm tries to reconnect, connects but freezes and errors out when setting difficulty. Any ideas?
Can't reproduce this, are you using some kind of proxy?
October 29, 2017, 07:43:20 PM
Can someone please tell me how to set the rig to mine with specific cards with this miner?
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
Is it really that hard to read a readme file?
Guess not...
Thanks (for being a dick)...I read the read me, I missed it before.
Is the dev command working for anyone else on 5.3? I tried it and it keeps crashing.
Lol, I gave you a hint, and you calling me a dick?
Wishing you best luck with your mining experience.
October 29, 2017, 06:32:05 PM
Hi
I'm still testing 0.5.3 on linux (14.04 LTS) driver 384, 1080Ti
so far 2-3% improvement over EWBF (with 1% fee, here is 2%)
CPU load is higher but not killer.
also testing on one of the 6x 1080s (driver 380), so far i haven't seen any difference in production at the pool.
the miner reports locally 3-4% more, but at the pool seems about the same.
will keep testing..
BTW: dstm, if you decide to add colors to the output, please put a switch that allow us to DISABLE it,
because in my case, i run a lot of scripting to read the real time data of the miner, and send it to a
webpage and to the LCD display of the miner, and dealing with colors is a pain in the ass
indkt.
I'm still testing 0.5.3 on linux (14.04 LTS) driver 384, 1080Ti
so far 2-3% improvement over EWBF (with 1% fee, here is 2%)
CPU load is higher but not killer.
also testing on one of the 6x 1080s (driver 380), so far i haven't seen any difference in production at the pool.
the miner reports locally 3-4% more, but at the pool seems about the same.
will keep testing..
BTW: dstm, if you decide to add colors to the output, please put a switch that allow us to DISABLE it,
because in my case, i run a lot of scripting to read the real time data of the miner, and send it to a
webpage and to the LCD display of the miner, and dealing with colors is a pain in the ass
indkt.
October 29, 2017, 05:50:36 PM
Can someone please tell me how to set the rig to mine with specific cards with this miner?
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
Is it really that hard to read a readme file?
Guess not...
Thanks (for being a dick)...I read the read me, I missed it before.
Is the dev command working for anyone else on 5.3? I tried it and it keeps crashing.
October 29, 2017, 05:30:34 PM
Can someone please tell me how to set the rig to mine with specific cards with this miner?
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
Is it really that hard to read a readme file?
Guess not...
October 29, 2017, 03:59:33 PM
Can someone please tell me how to set the rig to mine with specific cards with this miner?
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
in EWBF the command is "cuda_devices a b c d" but it doesn't work with this one.
Thanks
October 29, 2017, 03:19:30 PM
Great work on the miner.
I know CPU usage is an issue...but I'm running the latest version and my CPU usage is around 90% at all times. Is this still normal?
Also, is there a way to configure the start.bat file so the miner will mine from 2 or more different pools? Designate some cards to 1 pool and the remainder to another? Or do you have to open 2 instances of the miner with 2 different start files? I'm pretty sure my CPU couldn't handle that..LOL
I know CPU usage is an issue...but I'm running the latest version and my CPU usage is around 90% at all times. Is this still normal?
Also, is there a way to configure the start.bat file so the miner will mine from 2 or more different pools? Designate some cards to 1 pool and the remainder to another? Or do you have to open 2 instances of the miner with 2 different start files? I'm pretty sure my CPU couldn't handle that..LOL
How much of it does zm consume?
Yes, you have to open 2 instances.
With the miner running my CPU usage is 88%. The main draws are: system=37% CMD processor 29% System Interrupts 17%
With the miner off my CPU usage is 6-8%
Using EWBF my system interrupts are around 4% and total CPU usage is around 50%
Had the same issue with CPU usage, in my case it was msi afterburner causing it. Removed, rebooted and installed a fresh version sorted it for me. Well CPU still at ~20% but that's ok 😀
https://imgur.com/a/zOHUV
Windows 10 LTSB
Dstm 0.5.3
GeForce 388
Afterburner beta 19
I don't use afterburner. I use nvidia inspector...I send the settings to the card and then shut it down, so it's not even running in the background.
There seems to be a problem that this miner looks for (drivers?...but they are all up to date) that causes the system interrupt to hog CPU.
October 29, 2017, 12:47:58 PM
@dstm: pool closes connection (pool sexy), zm tries to reconnect, connects but freezes and errors out when setting difficulty. Any ideas?
Can't reproduce this, are you using some kind of proxy?
October 29, 2017, 12:29:32 PM
Hello guys! If you need some stability automatisations please use this (forum.z.cash)(bitcointalk) script.
So please let author work on main functionality, errors debugging and fixing will be in the end
Use script to fix your problems now.
So please let author work on main functionality, errors debugging and fixing will be in the end
Use script to fix your problems now.
October 29, 2017, 10:36:31 AM
Great improvement over EWBF of 5% across all my 6 x 1070 however dstm crashes every few moments as the .bat is on loop the miner restarts.
I find it strange why it crashes as with EWBF it is running for well over a month without issues?
I find it strange why it crashes as with EWBF it is running for well over a month without issues?
This is most likely due to overclocking, you have to readjust it, zm puts a different load on your GPUs.
Ok, I will try to retweak my overclocked settings and try again...
I also very often falls dstm. and very much rejected .. overclock cleaned, does not help ..
I had some reports about crashes after I released the windows version, however it seems that after people have readjusted their overclocking their issues were gone.
I've also no reports about unusual high reject rate.
Could you pls provide more information.
What OS, zm version, pool, how high is the reject rate, how does it crash etc.
Stability is of high priority.
OS Windows 10 64bit, zm version 0.5.3, pool nicehash, reject rate 3815/65 accepted/rejected, falls every 3-6 hours, writes overclocking, but overclocking is removed..
still noticed that the current hash is very different from the average!
http://ipic.su/img/img7/fs/1.1509222667.jpg
You'll get a higher reject rate on nicehash because they are submitting new jobs very often. ZM prepares work for the GPUs in advance, this is for performance reasons, it is especially helpful ins situation where you have cpu spikes caused by other processes. So if you get a new job it might happen that your solve a share for a previous job.
If you look at the average values, you'll see that they are increasing, since your current sol/s value is higher - so your performance was slower previously, maybe because some background process used cpu.
Edit: ZM writes also more details if it fails in this particular case, could you please provide the whole message?
will productivity increase in the next versions?
I'll work on performance after I'm done with current functionality requests.
October 29, 2017, 10:27:55 AM
Great improvement over EWBF of 5% across all my 6 x 1070 however dstm crashes every few moments as the .bat is on loop the miner restarts.
I find it strange why it crashes as with EWBF it is running for well over a month without issues?
I find it strange why it crashes as with EWBF it is running for well over a month without issues?
This is most likely due to overclocking, you have to readjust it, zm puts a different load on your GPUs.
Ok, I will try to retweak my overclocked settings and try again...
I also very often falls dstm. and very much rejected .. overclock cleaned, does not help ..
I had some reports about crashes after I released the windows version, however it seems that after people have readjusted their overclocking their issues were gone.
I've also no reports about unusual high reject rate.
Could you pls provide more information.
What OS, zm version, pool, how high is the reject rate, how does it crash etc.
Stability is of high priority.
OS Windows 10 64bit, zm version 0.5.3, pool nicehash, reject rate 3815/65 accepted/rejected, falls every 3-6 hours, writes overclocking, but overclocking is removed..
still noticed that the current hash is very different from the average!
http://ipic.su/img/img7/fs/1.1509222667.jpg
You'll get a higher reject rate on nicehash because they are submitting new jobs very often. ZM prepares work for the GPUs in advance, this is for performance reasons, it is especially helpful ins situation where you have cpu spikes caused by other processes. So if you get a new job it might happen that your solve a share for a previous job.
If you look at the average values, you'll see that they are increasing, since your current sol/s value is higher - so your performance was slower previously, maybe because some background process used cpu.
Edit: ZM writes also more details if it fails in this particular case, could you please provide the whole message?
will productivity increase in the next versions?
October 29, 2017, 10:19:56 AM
dstm, there is a real problem with your API.
Lets imagine we have mining proccess and suddenly connection to the Internet is lost:
So now we have lost connection and now let's chek your API:
So as you can see API shows everything is OK (we can see hashrates) but actually it's not (we don't have no connection actually).
And there is another problem. Even after getting connection your miner never reconnects (at least for me) - you have to relaunch it manually.
Could you fix it please?
Thank you!
P.S. I use Linux version (0.5.3).
Lets imagine we have mining proccess and suddenly connection to the Internet is lost:
Code:
...
> GPU0 50C Sol/s: 175.2 Sol/W: 2.64 Avg: 175.2 I/s: 92.3 Sh: 0.00 . .
> GPU1 47C Sol/s: 165.6 Sol/W: 2.50 Avg: 165.6 I/s: 92.3 Sh: 0.00 . .
> GPU2 47C Sol/s: 174.9 Sol/W: 2.65 Avg: 174.9 I/s: 93.3 Sh: 0.00 . .
> GPU3 50C Sol/s: 172.8 Sol/W: 2.64 Avg: 172.8 I/s: 92.1 Sh: 0.00 . .
> GPU4 44C Sol/s: 174.1 Sol/W: 2.59 Avg: 174.1 I/s: 95.5 Sh: 0.00 . .
> GPU5 46C Sol/s: 172.7 Sol/W: 2.62 Avg: 172.7 I/s: 93.6 Sh: 0.00 . .
========= Sol/s: 1035.3 Sol/W: 2.61 Avg: 1035.3 I/s: 559.2 Sh: 0.00 . .
GPU0 54C Sol/s: 170.7 Sol/W: 2.60 Avg: 172.9 I/s: 90.5 Sh: 0.00 . .
GPU1 51C Sol/s: 170.8 Sol/W: 2.54 Avg: 168.2 I/s: 90.5 Sh: 0.00 . .
GPU2 51C Sol/s: 168.3 Sol/W: 2.59 Avg: 171.6 I/s: 91.4 Sh: 0.00 . .
GPU3 54C Sol/s: 170.7 Sol/W: 2.60 Avg: 171.8 I/s: 90.3 Sh: 0.00 . .
GPU4 49C Sol/s: 179.2 Sol/W: 2.61 Avg: 176.7 I/s: 93.7 Sh: 0.00 . .
GPU5 51C Sol/s: 170.9 Sol/W: 2.59 Avg: 171.8 I/s: 91.6 Sh: 1.50 . . +
========= Sol/s: 1030.6 Sol/W: 2.59 Avg: 1033.0 I/s: 548.1 Sh: 1.50 . .
# connection closed by server r:2 - reconnecting...
# connection closed by server r:2 - reconnecting...
# server not responding - retrying...
# server not responding - retrying...
# server not responding - retrying...
...
So now we have lost connection and now let's chek your API:
Code:
{
"id": 1,
"result": [
{
"gpu_id": 0,
"temperature": 64,
"sol_ps": 168.72,
"avg_sol_ps": 170.36,
"sol_pw": 2.53,
"avg_sol_pw": 2.56,
"power_usage": 66.68,
"avg_power_usage": 66.42,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 1,
"temperature": 60,
"sol_ps": 168.46,
"avg_sol_ps": 169.18,
"sol_pw": 2.53,
"avg_sol_pw": 2.55,
"power_usage": 66.49,
"avg_power_usage": 66.4,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 2,
"temperature": 62,
"sol_ps": 170.42,
"avg_sol_ps": 169.03,
"sol_pw": 2.56,
"avg_sol_pw": 2.54,
"power_usage": 66.65,
"avg_power_usage": 66.66,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 3,
"temperature": 63,
"sol_ps": 169.64,
"avg_sol_ps": 168.74,
"sol_pw": 2.55,
"avg_sol_pw": 2.54,
"power_usage": 66.55,
"avg_power_usage": 66.39,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 4,
"temperature": 58,
"sol_ps": 171.91,
"avg_sol_ps": 173.99,
"sol_pw": 2.54,
"avg_sol_pw": 2.56,
"power_usage": 67.69,
"avg_power_usage": 68.08,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 5,
"temperature": 60,
"sol_ps": 172.03,
"avg_sol_ps": 171.91,
"sol_pw": 2.58,
"avg_sol_pw": 2.57,
"power_usage": 66.81,
"avg_power_usage": 66.78,
"accepted_shares": 0,
"rejected_shares": 0
}
],
"error": null
}So as you can see API shows everything is OK (we can see hashrates) but actually it's not (we don't have no connection actually).
And there is another problem. Even after getting connection your miner never reconnects (at least for me) - you have to relaunch it manually.
Could you fix it please?
Thank you!
P.S. I use Linux version (0.5.3).
This one is on my todo list already, I'll schedule it for the next release.
October 29, 2017, 10:17:11 AM
Help... was mining with zm --server zen.suprnova.cc --port 3618 --user user --pass x --telemetry=127.0.0.1:42000
After a day mining something else I tried to mine agaun and:
Thats it. GPU0 connets but nothing happens after that
No driver changes. Tried 0.5.2 and 0.5.3 - same result
any ideas?!
Current driver is 384.94, Win7, no cpu/mem usage...
ewbf or claymore for eth run just fine :?
After a day mining something else I tried to mine agaun and:
Code:
# zm 0.5.3
# GPU0+ GeForce GTX 1060 6GB MB: 6144 PCI: 5:0
# GPU1+ GeForce GTX 1060 3GB MB: 3072 PCI: 7:0
# GPU2+ GeForce GTX 1060 3GB MB: 3072 PCI: 8:0
# GPU3+ GeForce GTX 1060 3GB MB: 3072 PCI: 10:0
# telemetry server started
# GPU0 connected to: zen.suprnova.cc:3618
No driver changes. Tried 0.5.2 and 0.5.3 - same result
any ideas?!
Current driver is 384.94, Win7, no cpu/mem usage...
ewbf or claymore for eth run just fine :?
Thx, seems like there are still issues, will check.
October 29, 2017, 10:03:47 AM
dstm, there is a real problem with your API.
Lets imagine we have mining proccess and suddenly connection to the Internet is lost:
So now we have lost connection and now let's chek your API:
So as you can see API shows everything is OK (we can see hashrates) but actually it's not (we don't have no connection actually).
And there is another problem. Even after getting connection your miner never reconnects (at least for me) - you have to relaunch it manually.
Could you fix it please?
Thank you!
P.S. I use Linux version (0.5.3).
Lets imagine we have mining proccess and suddenly connection to the Internet is lost:
Code:
...
> GPU0 50C Sol/s: 175.2 Sol/W: 2.64 Avg: 175.2 I/s: 92.3 Sh: 0.00 . .
> GPU1 47C Sol/s: 165.6 Sol/W: 2.50 Avg: 165.6 I/s: 92.3 Sh: 0.00 . .
> GPU2 47C Sol/s: 174.9 Sol/W: 2.65 Avg: 174.9 I/s: 93.3 Sh: 0.00 . .
> GPU3 50C Sol/s: 172.8 Sol/W: 2.64 Avg: 172.8 I/s: 92.1 Sh: 0.00 . .
> GPU4 44C Sol/s: 174.1 Sol/W: 2.59 Avg: 174.1 I/s: 95.5 Sh: 0.00 . .
> GPU5 46C Sol/s: 172.7 Sol/W: 2.62 Avg: 172.7 I/s: 93.6 Sh: 0.00 . .
========= Sol/s: 1035.3 Sol/W: 2.61 Avg: 1035.3 I/s: 559.2 Sh: 0.00 . .
GPU0 54C Sol/s: 170.7 Sol/W: 2.60 Avg: 172.9 I/s: 90.5 Sh: 0.00 . .
GPU1 51C Sol/s: 170.8 Sol/W: 2.54 Avg: 168.2 I/s: 90.5 Sh: 0.00 . .
GPU2 51C Sol/s: 168.3 Sol/W: 2.59 Avg: 171.6 I/s: 91.4 Sh: 0.00 . .
GPU3 54C Sol/s: 170.7 Sol/W: 2.60 Avg: 171.8 I/s: 90.3 Sh: 0.00 . .
GPU4 49C Sol/s: 179.2 Sol/W: 2.61 Avg: 176.7 I/s: 93.7 Sh: 0.00 . .
GPU5 51C Sol/s: 170.9 Sol/W: 2.59 Avg: 171.8 I/s: 91.6 Sh: 1.50 . . +
========= Sol/s: 1030.6 Sol/W: 2.59 Avg: 1033.0 I/s: 548.1 Sh: 1.50 . .
# connection closed by server r:2 - reconnecting...
# connection closed by server r:2 - reconnecting...
# server not responding - retrying...
# server not responding - retrying...
# server not responding - retrying...
...
So now we have lost connection and now let's chek your API:
Code:
{
"id": 1,
"result": [
{
"gpu_id": 0,
"temperature": 64,
"sol_ps": 168.72,
"avg_sol_ps": 170.36,
"sol_pw": 2.53,
"avg_sol_pw": 2.56,
"power_usage": 66.68,
"avg_power_usage": 66.42,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 1,
"temperature": 60,
"sol_ps": 168.46,
"avg_sol_ps": 169.18,
"sol_pw": 2.53,
"avg_sol_pw": 2.55,
"power_usage": 66.49,
"avg_power_usage": 66.4,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 2,
"temperature": 62,
"sol_ps": 170.42,
"avg_sol_ps": 169.03,
"sol_pw": 2.56,
"avg_sol_pw": 2.54,
"power_usage": 66.65,
"avg_power_usage": 66.66,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 3,
"temperature": 63,
"sol_ps": 169.64,
"avg_sol_ps": 168.74,
"sol_pw": 2.55,
"avg_sol_pw": 2.54,
"power_usage": 66.55,
"avg_power_usage": 66.39,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 4,
"temperature": 58,
"sol_ps": 171.91,
"avg_sol_ps": 173.99,
"sol_pw": 2.54,
"avg_sol_pw": 2.56,
"power_usage": 67.69,
"avg_power_usage": 68.08,
"accepted_shares": 0,
"rejected_shares": 0
},
{
"gpu_id": 5,
"temperature": 60,
"sol_ps": 172.03,
"avg_sol_ps": 171.91,
"sol_pw": 2.58,
"avg_sol_pw": 2.57,
"power_usage": 66.81,
"avg_power_usage": 66.78,
"accepted_shares": 0,
"rejected_shares": 0
}
],
"error": null
}So as you can see API shows everything is OK (we can see hashrates) but actually it's not (we don't have no connection actually).
And there is another problem. Even after getting connection your miner never reconnects (at least for me) - you have to relaunch it manually.
Could you fix it please?
Thank you!
P.S. I use Linux version (0.5.3).
Jump to: