miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 22.

Xadja

newbie

Activity: 23

Merit: 0

Quote from: miniZ on July 31, 2020, 06:09:45 PM

Hi Xadja,
Could you tell us what algo are you mining, and the command line you are using?
Also, could you paste here the start of the log? We mean the log information that miniZ prints, before it starts mining.
Maybe we'll be able to understand what is going on then.
Thanks!
Cheers

Thank you for the answer!

Here is command line:

Code:

.\miniZ.exe --url=28acc5ea73280ffea8a8d2a61358f7c500c0c9eb132b0b3bb15eeb63f52fea65a3e@beam-eu.leafpool.com:3333 --par=beam3 --log --ocX

Here is log:

Code:

************ miniZ v1.6v5 ************
Number of CUDA[10.0] devices found: 1
Algo: EQ[beam3]
Pool#0: user[28acc5ea73280ffea8a8d2a61358f7c500c0c9eb132b0b3bb15eeb63f52fea65a3e]
server[beam-eu.leafpool.com] port[3333] ssl[no] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Logging:: file[miniZ.log] period[10] delay[0]
Optimisation: ocX[0]

miniZ

member

Activity: 690

Merit: 17

Quote from: Xadja on July 30, 2020, 11:11:59 PM

Guys, Why do I have 0 hashrate?

Code:

miniZ<144,5s>[06:0:00:6747]: Selecting GPU#0[0] GeForce RTX 2060 SUPER
[ 0d 0h 0m06s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s 42( 42.2)W clk=1470MHz mclk=6801MHz Sol/W=0.00
[ 0d 0h 0m10s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s 42( 42.2)W clk=1470MHz mclk=6801MHz Sol/W=0.00
[ 0d 0h 0m20s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s 42( 41.5)W clk=1470MHz mclk=6801MHz Sol/W=0.00

I tried to use miniZ on different machines and got the same result.
Thanks.

Hi Xadja,
Could you tell us what algo are you mining, and the command line you are using?
Also, could you paste here the start of the log? We mean the log information that miniZ prints, before it starts mining.
Maybe we'll be able to understand what is going on then.
Thanks!
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: MineOrDie on July 29, 2020, 03:42:35 AM

That's OC1. OC2 works, but I see no improvement over 1.5t2.
About running with less GPUs - I cannot try that. I'm only able to remote control my rigs at the moment. Maybe set the miner only to use 1 GPU.

Hi MineOrDie,
Thanks for the feedback.
We're looking into it.
We were suggesting to mine with less gpus but not physically removing the GPUs, by using -cd, for example.

Cheers

Xadja

newbie

Activity: 23

Merit: 0

Guys, Why do I have 0 hashrate?

Code:

miniZ<144,5s>[06:0:00:6747]: Selecting GPU#0[0] GeForce RTX 2060 SUPER
[ 0d 0h 0m06s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s 42( 42.2)W clk=1470MHz mclk=6801MHz Sol/W=0.00
[ 0d 0h 0m10s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s 42( 42.2)W clk=1470MHz mclk=6801MHz Sol/W=0.00
[ 0d 0h 0m20s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s 42( 41.5)W clk=1470MHz mclk=6801MHz Sol/W=0.00

I tried to use miniZ on different machines and got the same result.
Thanks.

MineOrDie

jr. member

Activity: 75

Merit: 1

Quote from: miniZ on July 28, 2020, 05:02:05 PM

Hi MineOrDie,
Thank you for all the feedback. It is really important since it helps us to make miniZ better.

We could not reproduce this issue. Have you tried to run it with --oc1 or --oc2? Also, does it work if you run with less GPUs?
(Btw, f11 was only working for 144,5, it was removed on version 1.5u and now it is ignored.)

It is a bit frustrating for us when we cannot reproduce the issues, it becomes much harder to fix them.
We'll keep looking into this.
Cheers

Code:

miniZ<125,4>[14:0:00:2904]: Selecting GPU#1[1] GeForce GTX 1060 3GB
miniZ<125,4>[14:0:00:2904]: Selecting GPU#5[5] GeForce GTX 1060 3GB
miniZ<125,4>[14:0:00:2904]: Selecting GPU#3[3] GeForce GTX 1060 3GB
miniZ<125,4>[14:0:00:2904]: Selecting GPU#2[2] GeForce GTX 1060 3GB
miniZ<125,4>[14:0:00:2904]: Selecting GPU#4[4] GeForce GTX 1060 3GB
miniZ<125,4>[16:0:00:2814]: Selecting GPU#0[0] GeForce GTX 1060 3GB
[FATAL ] Cannot load deviceZ code.
[INFO ] Disconnecting from zel.2miners.com
[INFO ]zel.2miners.com Stopping miner
[INFO ] Miner monitor exited.

That's OC1. OC2 works, but I see no improvement over 1.5t2.
About running with less GPUs - I cannot try that. I'm only able to remote control my rigs at the moment. Maybe set the miner only to use 1 GPU.

miniZ

member

Activity: 690

Merit: 17

Quote from: MineOrDie on July 28, 2020, 12:24:51 PM

Quote from: miniZ on July 28, 2020, 09:14:49 AM

Quote from: MineOrDie on July 28, 2020, 03:06:30 AM

Well, it's a hell of an unstable kernel then. I cannot even run it on 0 / 0. Just adjusting my power. I'm reverting back to 1.5t2. Can you test it out on a 1060 3GB?

Hi MineOrDie,
Do you also have issues with t3?
Thanks for your feedback, we are going to look into it carefuly.
Cheers

Nope, t3 has that strange memory allocation bug on 3GB cards mining ZEL. Then I think there was another version that had a bug that caused the miner to operate in mode 10 even if I'm running Windows 8.1.
The latest one fixed everything, but it's a mess again...
I know you work hard, so really appreciate it.

Hi MineOrDie,
Thank you for all the feedback. It is really important since it helps us to make miniZ better.

We could not reproduce this issue. Have you tried to run it with --oc1 or --oc2? Also, does it work if you run with less GPUs?
(Btw, f11 was only working for 144,5, it was removed on version 1.5u and now it is ignored.)

It is a bit frustrating for us when we cannot reproduce the issues, it becomes much harder to fix them.
We'll keep looking into this.
Cheers

MineOrDie

jr. member

Activity: 75

Merit: 1

Quote from: miniZ on July 28, 2020, 09:14:49 AM

Quote from: MineOrDie on July 28, 2020, 03:06:30 AM

Well, it's a hell of an unstable kernel then. I cannot even run it on 0 / 0. Just adjusting my power. I'm reverting back to 1.5t2. Can you test it out on a 1060 3GB?

Hi MineOrDie,
Do you also have issues with t3?
Thanks for your feedback, we are going to look into it carefuly.
Cheers

Nope, t3 has that strange memory allocation bug on 3GB cards mining ZEL. Then I think there was another version that had a bug that caused the miner to operate in mode 10 even if I'm running Windows 8.1.
The latest one fixed everything, but it's a mess again...
I know you work hard, so really appreciate it.

miniZ

member

Activity: 690

Merit: 17

Quote from: MineOrDie on July 28, 2020, 03:06:30 AM

Well, it's a hell of an unstable kernel then. I cannot even run it on 0 / 0. Just adjusting my power. I'm reverting back to 1.5t2. Can you test it out on a 1060 3GB?

Hi MineOrDie,
Do you also have issues with t3?
Thanks for your feedback, we are going to look into it carefuly.
Cheers

MineOrDie

jr. member

Activity: 75

Merit: 1

Quote from: miniZ on July 27, 2020, 07:52:29 PM

Quote from: MineOrDie on July 26, 2020, 03:06:47 PM

Mining ZEL on 1060 3GB, Windows 10, latest drivers.

Code:

[FATAL ] GPU[4]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[1]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[2]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[0]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[3]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[5]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[INFO ] Disconnecting from zel.2miners.com
[INFO ]zel.2miners.com Stopping miner
[INFO ] Miner monitor exited.
[INFO ] Exited main loop

Can you help me out? Same OC settings like on 1.5.

Hi MineOrDie,
These CUDA errors you're getting really seam related to OCs.
Because we did changes to the kernels it can happen that some adjustments to the OC are required too.
It is possilbe that it became unstable to only one of the GPU. You can start by adjusting the first one that gave the error, however if the rig crashes again maybe it is good to adjust the others.
Let us know if you managed to make it more stable.
Cheers

Well, it's a hell of an unstable kernel then. I cannot even run it on 0 / 0. Just adjusting my power. I'm reverting back to 1.5t2. Can you test it out on a 1060 3GB?

miniZ

member

Activity: 690

Merit: 17

Quote from: MineOrDie on July 26, 2020, 03:06:47 PM

Mining ZEL on 1060 3GB, Windows 10, latest drivers.

Code:

[FATAL ] GPU[4]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[1]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[2]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[0]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[3]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[5]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[INFO ] Disconnecting from zel.2miners.com
[INFO ]zel.2miners.com Stopping miner
[INFO ] Miner monitor exited.
[INFO ] Exited main loop

Can you help me out? Same OC settings like on 1.5.

Hi MineOrDie,
These CUDA errors you're getting really seam related to OCs.
Because we did changes to the kernels it can happen that some adjustments to the OC are required too.
It is possilbe that it became unstable to only one of the GPU. You can start by adjusting the first one that gave the error, however if the rig crashes again maybe it is good to adjust the others.
Let us know if you managed to make it more stable.
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: Star65 on July 26, 2020, 09:45:51 AM

Hi, miniZ! Can you add a hotkey for starting ocX again? My rig is crashed on the exit and I must restart comp every times. I use W7 with ConEmu.
Thanks for the nice miner, bro!

Hi Star65,
Thank you for contacting us.
We are not sure whether we have properly understood your suggestion

Maybe, you can clarify us a little, giving a few more details?
Cheers

MineOrDie

jr. member

Activity: 75

Merit: 1

Mining ZEL on 1060 3GB, Windows 10, latest drivers.

Code:

************ miniZ v1.6v5 ************
Number of CUDA[10.0] devices found: 6
Algo: EQ[125,4]
Pool#0: user[t1SNnYcs4Z4u9uKPLDMfBzVWfDbtkCs8Pwb.RIG2-1060GAMINGX-3GB]
server[zel.2miners.com] port[19090] ssl[yes] pers[ZelProof]
Optimisation: f11[0 1 2 3 4 5]
Temp. limit: [90°C]
miniZ<125,4>[00:0:00:2904]: Selecting GPU#3[3] GeForce GTX 1060 3GB
miniZ<125,4>[00:0:00:2904]: Selecting GPU#5[5] GeForce GTX 1060 3GB
miniZ<125,4>[00:0:00:2904]: Selecting GPU#2[2] GeForce GTX 1060 3GB
miniZ<125,4>[16:0:00:2807]: Selecting GPU#0[0] GeForce GTX 1060 3GB
miniZ<125,4>[00:0:00:2904]: Selecting GPU#1[1] GeForce GTX 1060 3GB
miniZ<125,4>[00:0:00:2904]: Selecting GPU#4[4] GeForce GTX 1060 3GB
[ 0d 0h 0m06s] S: 0/0 237(236.7)Sol/s 137(137.1)W [zel.2miners.com]- 38ms
0>GTX 1060 3GB S: 0/0 [43°C/44%] 0.00 I/s 0.0(0.0)Sol/s 24( 24.1)W clk=1328MHz mclk=3007MHz Sol/W=0.00
1>GTX 1060 3GB S: 0/0 [43°C/43%] 0.00 I/s 0.0(0.0)Sol/s 23( 23.4)W clk=1379MHz mclk=3007MHz Sol/W=0.00
2>GTX 1060 3GB S: 0/0 [39°C/40%] 0.30 I/s 0.8(0.8)Sol/s 22( 21.5)W clk=1366MHz mclk=3007MHz Sol/W=0.04
3>GTX 1060 3GB S: 0/0 [44°C/44%] 0.00 I/s 0.0(0.0)Sol/s 23( 22.6)W clk=1303MHz mclk=3007MHz Sol/W=0.00
4>GTX 1060 3GB S: 0/0 [42°C/42%] 0.00 I/s 0.0(0.0)Sol/s 23( 22.8)W clk=1366MHz mclk=3007MHz Sol/W=0.00
5>GTX 1060 3GB S: 0/0 [45°C/45%] 0.30 I/s 0.8(0.8)Sol/s 23( 22.6)W clk=1316MHz mclk=3007MHz Sol/W=0.03
[ 0d 0h 0m10s] S: 0/0 224(224.3)Sol/s 137(137.1)W [zel.2miners.com]- 38ms
0>GTX 1060 3GB S: 0/0 [43°C/44%] 7.95 I/s 15.9(15.9)Sol/s 24( 24.1)W clk=1328MHz mclk=3007MHz Sol/W=0.66
1>GTX 1060 3GB S: 0/0 [43°C/43%] 8.96 I/s 17.9(17.9)Sol/s 23( 23.4)W clk=1379MHz mclk=3007MHz Sol/W=0.76
2>GTX 1060 3GB S: 0/0 [39°C/40%] 8.40 I/s 16.8(16.8)Sol/s 22( 21.5)W clk=1366MHz mclk=3007MHz Sol/W=0.78
3>GTX 1060 3GB S: 0/0 [44°C/44%] 8.49 I/s 16.9(16.9)Sol/s 23( 22.6)W clk=1303MHz mclk=3007MHz Sol/W=0.75
4>GTX 1060 3GB S: 0/0 [42°C/42%] 0.00 I/s 0.0( 0.0)Sol/s 23( 22.8)W clk=1366MHz mclk=3007MHz Sol/W=0.00
5>GTX 1060 3GB S: 0/0 [45°C/45%] 8.63 I/s 17.2(17.2)Sol/s 23( 22.6)W clk=1316MHz mclk=3007MHz Sol/W=0.76
[FATAL ] GPU[4]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[1]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[2]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[0]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[3]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL ] GPU[5]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[INFO ] Disconnecting from zel.2miners.com
[INFO ]zel.2miners.com Stopping miner
[INFO ] Miner monitor exited.
[INFO ] Exited main loop

Can you help me out? Same OC settings like on 1.5.

Star65

member

Activity: 109

Merit: 13

Hi, miniZ! Can you add a hotkey for starting ocX again? My rig is crashed on the exit and I must restart comp every times. I use W7 with ConEmu.
Thanks for the nice miner, bro!

somaton

jr. member

Activity: 212

Merit: 6

Hi, yes, 1.6v5 fixed that problem for me, thanks.

miniZ

member

Activity: 690

Merit: 17

Quote from: richtm on July 22, 2020, 07:10:23 AM

I installed the latest version 1.6v4 with algo 125/4. On two different rigs the last 6 gpus don't show the power usage or temperature.

0d 0h16m00s] 493(482.8)Sol/s 919(908.3)W- 255ms
0>GTX 1070 `91.7% [62°C/32%] 17.77 I/s 35.9(34.8)Sol/s 115(110.4)W clk=1620MHz mclk=3999MHz Sol/W=0.31
1>GTX 1070 ` 100% [62°C/46%] 17.42 I/s 33.7(33.6)Sol/s 113(108.9)W clk=1594MHz mclk=3999MHz Sol/W=0.31

when I go back to version 1.6v3 everything is good.

Quote from: somaton on July 22, 2020, 10:56:08 AM

i see same problem with one rig (two more does not have this problem) with 1.6v4, everything is fine with 1.6v3. All cards seems to have same temperature and fan speed, but it is not correct.

[ 0d21h25m10s|18:42:50 22/07/2020] S:4601/27 116(116.7)Sol/s 898(904.1)W [Beam-PoW]- 86ms

Hi richtm, somaton,
Thank you for reporting this. We had also another miner reporting the same.
It seems that it was not happening in all systems.

If you go to Download page you can find miniZ v1.6v5 that fixes this.

Let us know if it worked (or not) for you.

Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: UselessGuru on July 22, 2020, 12:23:27 AM

Quote

...
Regarding your issue with the rejected shares, indeed you seem to have a bit more than the others.
Could you try running miniZ without the --cleanjobs? We suspect that it may be causing this.
Let us know if this helped.

Without --cleanjob I am seeing no rejected shares.

[ 0d 0h11m10s] S: 16/0 0>GTX 1060 6GB ` 100% [65°C/40%]*6.43 I/s 13.1(12.5)Sol/s 132(129.8)W clk=1974MHz mclk=4498MHz Sol/W=0.10 [BEAMV3.eu.nicehash.com,Beam-PoW]- 34ms (88.5%) (11.5%)

And more importantly it finds much more shares 16(0) in 11 minutes ('without --cleanjobs') as compared to 2(4) in 10 minutes ('with --cleanjobs')

Hi UselessGuru,

Thanks for reporting that this solves your issue.

The --cleanjobs is only supported by a small subset of pools, we are not aware of any beam pools that support it.

Cheers

somaton

jr. member

Activity: 212

Merit: 6

i see same problem with one rig (two more does not have this problem) with 1.6v4, everything is fine with 1.6v3. All cards seems to have same temperature and fan speed, but it is not correct.

[ 0d21h25m10s|18:42:50 22/07/2020] S:4601/27 116(116.7)Sol/s 898(904.1)W [Beam-PoW]- 86ms
0>GTX 1080 Ti S:1096/8 [72°C/94%] 13.80 I/s 27.8(27.4)Sol/s 223(225.1)W clk=1645MHz mclk=5508MHz Sol/W=0.12
1>GTX 1080 Ti S:1185/6 [72°C/94%] 15.58 I/s 30.5(30.8)Sol/s 223(224.7)W clk=1645MHz mclk=5508MHz Sol/W=0.14
2>GTX 1080 Ti S:1115/6 [72°C/94%] 14.23 I/s 28.1(28.3)Sol/s 225(224.7)W clk=1645MHz mclk=5508MHz Sol/W=0.13
3>GTX 1080 Ti S:1180/7 [72°C/94%]*15.16 I/s 29.7(30.2)Sol/s 226(224.2)W clk=1645MHz mclk=5508MHz Sol/W=0.13

UselessGuru: Thanks for your tip, i know about profileinspector and p2, i have this utility on all my rigs, but did not tried it with beam3. With some algos disabling p2 will lower hashrate.

richtm

newbie

Activity: 1

Merit: 0

I installed the latest version 1.6v4 with algo 125/4. On two different rigs the last 6 gpus don't show the power usage or temperature.

0d 0h16m00s] 493(482.8)Sol/s 919(908.3)W- 255ms
  0>GTX 1070 `91.7% [62°C/32%] 17.77 I/s 35.9(34.8)Sol/s 115(110.4)W clk=1620MHz mclk=3999MHz Sol/W=0.31
  1>GTX 1070 ` 100% [62°C/46%] 17.42 I/s 33.7(33.6)Sol/s 113(108.9)W clk=1594MHz mclk=3999MHz Sol/W=0.31
  2>GTX 1070 Ti ` 100% [61°C/32%] 19.47 I/s 38.6(37.7)Sol/s 116(123.3)W clk=1506MHz mclk=3999MHz Sol/W=0.31
  3>GTX 1070 Ti ` 100% [65°C/41%] 18.87 I/s 38.0(36.7)Sol/s 129(122.3)W clk=1506MHz mclk=3999MHz Sol/W=0.30
  4>GTX 1070 ` 100% [63°C/41%] 17.47 I/s 35.2(33.9)Sol/s 113(111.9)W clk=1594MHz mclk=3999MHz Sol/W=0.30
  5>GTX 1070 ` 100% [65°C/46%] 17.39 I/s 34.6(34.0)Sol/s 112(111.0)W clk=1594MHz mclk=3999MHz Sol/W=0.31
  6>GTX 1070 ` 100% [64°C/50%] 17.73 I/s 35.0(34.0)Sol/s 114(111.1)W clk=1607MHz mclk=3999MHz Sol/W=0.31
  7>GTX 1070 ` 100% [63°C/33%] 17.14 I/s 33.5(33.2)Sol/s 108(109.5)W clk=1531MHz mclk=3999MHz Sol/W=0.30
  8>GTX 1070 ` 100% [0°C/ 0%] 17.60 I/s 34.9(34.5)Sol/s 0( 0.0)W clk=1784MHz mclk=4004MHz Sol/W=inf
  9>GTX 1070 ` 100% [0°C/ 0%] 17.56 I/s 34.7(34.0)Sol/s 0( 0.0)W clk=1784MHz mclk=4004MHz Sol/W=inf
10>GTX 1070 ` 100% [0°C/ 0%] 17.58 I/s 35.2(34.5)Sol/s 0( 0.0)W clk=1683MHz mclk=4004MHz Sol/W=inf
11>GTX 1070 ` 100% [0°C/ 0%] 17.45 I/s 35.7(34.4)Sol/s 0( 0.0)W clk=1683MHz mclk=4004MHz Sol/W=inf
12>GTX 1070 ` 100% [0°C/ 0%] 17.56 I/s 34.6(34.2)Sol/s 0( 0.0)W clk=1746MHz mclk=4004MHz Sol/W=inf
13>GTX 1070 ` 100% [0°C/ 0%] 17.14 I/s 33.4(33.4)Sol/s 0( 0.0)W clk=1683MHz mclk=4004MHz Sol/W=inf

when I go back to version 1.6v3 everything is good.

UselessGuru

jr. member

Activity: 200

Merit: 3

Quote

...
Regarding your issue with the rejected shares, indeed you seem to have a bit more than the others.
Could you try running miniZ without the --cleanjobs? We suspect that it may be causing this.
Let us know if this helped.

Without --cleanjob I am seeing no rejected shares.

[ 0d 0h11m10s] S: 16/0 0>GTX 1060 6GB ` 100% [65°C/40%]*6.43 I/s 13.1(12.5)Sol/s 132(129.8)W clk=1974MHz mclk=4498MHz Sol/W=0.10 [BEAMV3.eu.nicehash.com,Beam-PoW]- 34ms (88.5%) (11.5%)

And more importantly it finds much more shares 16(0) in 11 minutes ('without --cleanjobs') as compared to 2(4) in 10 minutes ('with --cleanjobs')

miniZ

member

Activity: 690

Merit: 17

Quote from: cryptosize on July 21, 2020, 02:18:48 PM

Same here.

Quote from: somaton on July 21, 2020, 11:31:12 AM

[ 0d19h21m00s|19:27:05 21/07/2020] S:4116/49 133(133.2)Sol/s 1070(1077.1)W- 81ms

0>RTX 2080 SUPER S:925/12 [75°C/65%] 15.09 I/s 30.2(30.2)Sol/s 238(238.7)W clk=1920MHz mclk=7500MHz Sol/W=0.13
1>RTX 2080 Ti S:1393/24 [76°C/66%] 22.02 I/s 43.8(44.0)Sol/s 285(284.2)W clk=1785MHz mclk=6800MHz Sol/W=0.15
2>GTX 1080 Ti S:877/6 [74°C/71%] 14.44 I/s 28.9(28.7)Sol/s 274(277.9)W clk=1784MHz mclk=5005MHz Sol/W=0.10
3>RTX 2080 SUPER S:912/7 [73°C/72%] 15.11 I/s 30.3(30.2)Sol/s 273(275.3)W clk=1784MHz mclk=5005MHz Sol/W=0.11

there is some rejects with beam3 compared to other algos, but not 50%. Dont see any rejects with other algos i tried, so some more work needed with beam3.

Hi somaton, cryptosize,
Thank you for the feedback.

We had noticed what seemed a slight increase of rejected shares ( maybe up to 1% but not more) . Yet, in our tests, the improvements were clearly overcoming this "annoyance" so we decided to proceed with the release.
We will work to solve the issue!

However, if you are experiencing high value of rejected shares do let us know.
Cheers

Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 22. (Read 59795 times)