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

miniZ

member

Activity: 690

Merit: 17

Quote from: Asusrogmining on August 31, 2019, 03:47:26 PM

Hi,
What is the command of these parameters?

retry counts
retry delay
job timeout

Awesomeminer would close the miniz in case of a connection error even if it was for 30 minutes or less!

Hi Asusrogmining,
if we correctly understood your question, miniZ does not have a command for these parameters.
Maybe you could elaborate a bit more and let us know if you need us to add some features.

Thanks.
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: devivier on August 30, 2019, 03:56:17 AM

Hello
I posede two rtx card 2060 one asus and the other msi aventus oc
can you help me find the right oc to exploit the beam BeamHashII I'm on cudominer
know the tdp? clokc? memory
for msi it is impossible to load the tdp below 78
tanks you

Hi devivier,
Unfortunately we do not have a 2060 card so we cannot share any values.
These are the ones we usually have an easy access to.
The tables are updated when we make changes to miner, so it is good to check it every now and then for updated values.

We did a search and found this forum discussion https://forums.anandtech.com/threads/help-overclocking-rtx-2060.2562400/.
Maybe this can help you get started in finding the best OC values for your card and configuration.

Hope this helps.
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: Divinity666 on August 30, 2019, 01:40:26 AM

Quote from: miniZ on August 29, 2019, 02:51:48 PM

Hi Divinity666,
we just released a v1.5q3 beta version.
Could you test it and let us know if you get the same issue?
Thank you.
Cheers

No, nothing has changed(

Hi Divinity666,
Thank you for the feedback.
Tomorrow we will update beta version, could you try it out then and check if you still have the same issue with the miner stopping too long when it loses connection?
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: BigHarryArmsi on August 29, 2019, 02:14:35 PM

Thanks for the note.
Yes, I am disappointed at the hash rates especially when I see others with 60s for their 1080TIs!
My 1060s are running a little better after some hours ~21, 1080 ~42 Power at 65% and 79% respectively and all clocks at 140 and 400. It seems to make little difference with my OC setting but power makes a noticeable difference. Drivers are all 430+
1080TIs are running ~56 (Blecch!) at 80% and clocks at 140-400 again. (still experimenting there) Power is a big deal, here. Drivers are 419+
Both rigs running on Win10 with G3930 CPUs. CPU use is way down from 144_5! Thanks a bundle for that! OC1 serious decreases, OC2 slightly slower so running with neither at this point.
Any suggestions to get these speeded up are greatly appreciated! Anyone?

Thanks again for all the help.

Hi BigHarryArmsi,
how is it going with the OCs?

Based on some values that people have been sharing around we realize that PL~70% (give or take 5%) is the most common power used by miners.
We tried some values for clocks core and memory for the 1080 that we share here for your (and others) reference.
1080: PL=70% (126W), core=+150, memory=+900 resulted in ~40.7 Sol/s. T~65C, Fan~42%.

Tomorrow we plan an update to beta version, could you try then the 1060 6GB and check if there was any improvement?
Thanks!
Cheers

Asusrogmining

newbie

Activity: 24

Merit: 0

Quote from: miniZ on August 29, 2019, 02:56:33 PM

Quote from: darkneorus on August 25, 2019, 01:46:35 PM

Quote from: miniZ on August 25, 2019, 01:39:54 PM

Could you just confirm that mode 3 was selected? Should appear something like this in the beginning of output:
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#0[0] P104-100

yup
GPU Bus load, reported by GPU-Z, also varies from 7 to 16%, with worst performing GPUs using less bus bandwidth.

Hi darkneorus,
we just released a v1.5q3 beta version.
Could you check if there is any improvement for the P104?
Thanks.
Cheers

Hi,
What is the command of these parameters?

retry counts
retry delay
job timeout

Awesomeminer would close the miniz in case of a connection error even if it was for 30 minutes or less!

devivier

newbie

Activity: 36

Merit: 0

Hello
I posede two rtx card 2060 one asus and the other msi aventus oc
can you help me find the right oc to exploit the beam BeamHashII I'm on cudominer
know the tdp? clokc? memory
for msi it is impossible to load the tdp below 78
tanks you

Divinity666

jr. member

Activity: 312

Merit: 2

Quote from: miniZ on August 29, 2019, 02:51:48 PM

Hi Divinity666,
we just released a v1.5q3 beta version.
Could you test it and let us know if you get the same issue?
Thank you.
Cheers

No, nothing has changed(

BigHarryArmsi

newbie

Activity: 137

Merit: 0

Quote from: miniZ on August 29, 2019, 02:52:59 PM

Quote from: BigHarryArmsi on August 29, 2019, 02:14:35 PM

Thanks for the note.
Yes, I am disappointed at the hash rates especially when I see others with 60s for their 1080TIs!
My 1060s are running a little better after some hours ~21, 1080 ~42 Power at 65% and 79% respectively and all clocks at 140 and 400. It seems to make little difference with my OC setting but power makes a noticeable difference. Drivers are all 430+
1080TIs are running ~56 (Blecch!) at 80% and clocks at 140-400 again. (still experimenting there) Power is a big deal, here. Drivers are 419+
Both rigs running on Win10 with G3930 CPUs. CPU use is way down from 144_5! Thanks a bundle for that! OC1 serious decreases, OC2 slightly slower so running with neither at this point.
Any suggestions to get these speeded up are greatly appreciated! Anyone?

Thanks again for all the help.

Hi BigHarryArmsi,
thanks for for the information on cpu usage. It is good to know.
Indeed we introduced some changes, you were the first giving some feedback on this.

We will try to improve the oc1/oc2 for the next release.

We will also check again our OC values for the 1080s. But, maybe someone would like to share here their values.

Cheers

By the by. The 1080TI rig percentages are all green. The 1060 rig is all orange except for one red.

miniZ

member

Activity: 690

Merit: 17

Quote from: darkneorus on August 25, 2019, 01:46:35 PM

Quote from: miniZ on August 25, 2019, 01:39:54 PM

Could you just confirm that mode 3 was selected? Should appear something like this in the beginning of output:
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#0[0] P104-100

yup
GPU Bus load, reported by GPU-Z, also varies from 7 to 16%, with worst performing GPUs using less bus bandwidth.

Hi darkneorus,
we just released a v1.5q3 beta version.
Could you check if there is any improvement for the P104?
Thanks.
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: BigHarryArmsi on August 29, 2019, 02:14:35 PM

Thanks for the note.
Yes, I am disappointed at the hash rates especially when I see others with 60s for their 1080TIs!
My 1060s are running a little better after some hours ~21, 1080 ~42 Power at 65% and 79% respectively and all clocks at 140 and 400. It seems to make little difference with my OC setting but power makes a noticeable difference. Drivers are all 430+
1080TIs are running ~56 (Blecch!) at 80% and clocks at 140-400 again. (still experimenting there) Power is a big deal, here. Drivers are 419+
Both rigs running on Win10 with G3930 CPUs. CPU use is way down from 144_5! Thanks a bundle for that! OC1 serious decreases, OC2 slightly slower so running with neither at this point.
Any suggestions to get these speeded up are greatly appreciated! Anyone?

Thanks again for all the help.

Hi BigHarryArmsi,
thanks for for the information on cpu usage. It is good to know.
Indeed we introduced some changes, you were the first giving some feedback on this.

We will try to improve the oc1/oc2 for the next release.

We will also check again our OC values for the 1080s. But, maybe someone would like to share here their values.

Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: miniZ on August 29, 2019, 01:16:36 PM

Quote from: Divinity666 on August 29, 2019, 12:51:17 PM

Pool is 2miners.com, I'm using latest version of miner, but this happened on every version I used before. So why would miner drop connection anyway? Or why it waits for minutes to reconnect rather do it right away?

Hi Divinity666,
Thank you for the information.
The miner should be continuously trying to reconnect.
We will investigate this better, we're trying to reproduce this on 2miners.
Cheers

Hi Divinity666,
we just released a v1.5q3 beta version.
Could you test it and let us know if you get the same issue?
Thank you.
Cheers

BigHarryArmsi

newbie

Activity: 137

Merit: 0

Quote from: miniZ on August 29, 2019, 01:12:56 PM

Quote from: BigHarryArmsi on August 29, 2019, 12:32:34 AM

Thanks for all the help!

Both oc1 and oc2 slowed my hashing. OC1 especially, so I am running without either.
5)6gb MSI 1060s 65%-140-400 are ~20, MSI 1080 70%-135-350 is ~40
146 Sols at ~530w

Hi BigHarryArmsi,
we do not have a 1060 6GB, but on our 1060 3GB and with oc values shown here (table 2, eco) we get only a bit less than what you show.
Our power is at 50%, in there we were aiming for efficiency...maybe a bit extreme for some. The core and mem combination may not be the best for your GPU. Maybe try to tweak a bit your OCs, it looks that with 65% and your 1060 6GB you should get a bit more than 20Sol/s.

We will revise the --oc1 parameter.
Thank you for the feedback.
Cheers

Thanks for the note.
Yes, I am disappointed at the hash rates especially when I see others with 60s for their 1080TIs!
My 1060s are running a little better after some hours ~21, 1080 ~42 Power at 65% and 79% respectively and all clocks at 140 and 400. It seems to make little difference with my OC setting but power makes a noticeable difference. Drivers are all 430+
1080TIs are running ~56 (Blecch!) at 80% and clocks at 140-400 again. (still experimenting there) Power is a big deal, here. Drivers are 419+
Both rigs running on Win10 with G3930 CPUs. CPU use is way down from 144_5! Thanks a bundle for that! OC1 serious decreases, OC2 slightly slower so running with neither at this point.
Any suggestions to get these speeded up are greatly appreciated! Anyone?

Thanks again for all the help.

miniZ

member

Activity: 690

Merit: 17

Quote from: Divinity666 on August 29, 2019, 12:51:17 PM

Pool is 2miners.com, I'm using latest version of miner, but this happened on every version I used before. So why would miner drop connection anyway? Or why it waits for minutes to reconnect rather do it right away?

Hi Divinity666,
Thank you for the information.
The miner should be continuously trying to reconnect.
We will investigate this better, we're trying to reproduce this on 2miners.
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: BigHarryArmsi on August 29, 2019, 12:32:34 AM

Thanks for all the help!

Both oc1 and oc2 slowed my hashing. OC1 especially, so I am running without either.
5)6gb MSI 1060s 65%-140-400 are ~20, MSI 1080 70%-135-350 is ~40
146 Sols at ~530w

Hi BigHarryArmsi,
we do not have a 1060 6GB, but on our 1060 3GB and with oc values shown here (table 2, eco) we get only a bit less than what you show.
Our power is at 50%, in there we were aiming for efficiency...maybe a bit extreme for some. The core and mem combination may not be the best for your GPU. Maybe try to tweak a bit your OCs, it looks that with 65% and your 1060 6GB you should get a bit more than 20Sol/s.

We will revise the --oc1 parameter.
Thank you for the feedback.
Cheers

Divinity666

jr. member

Activity: 312

Merit: 2

Pool is 2miners.com, I'm using latest version of miner, but this happened on every version I used before. So why would miner drop connection anyway? Or why it waits for minutes to reconnect rather do it right away?

miniZ

member

Activity: 690

Merit: 17

Quote from: Divinity666 on August 29, 2019, 07:20:13 AM

Hi, MiniZ! Could you plz explain what's happening here: cards will periodically start idling for 1-2 mins until I\s and h\r start dropping and then "come back to live". Why doesn't miner show any error or something and why I\s h\r holding for 1-2 minutes when cards are idling??

Hi Divinity666,
this may happen if the miner loses connection to the mining pool at some point.
For example, if there were no shares submitted for some time the connection can drop. And it restarts mining when connection is possible.

We are having a look in any case. Could you let us know what miniZ version are you using? And pool?
You use Windows 10 right? Mining Beam?
Thanks.
Cheers

Divinity666

jr. member

Activity: 312

Merit: 2

Hi, MiniZ! Could you plz explain what's happening here: cards will periodically start idling for 1-2 mins until I\s and h\r start dropping and then "come back to live". Why doesn't miner show any error or something and why I\s h\r holding for 1-2 minutes when cards are idling??

Quote

[ 2d 2h10m00s|15:11:42 29/08/2019] 134(133.8)Sol/s 275(271.6)W
0>GTX 1080 ` 100% [54шC/29%] 33.45 I/s 66.5(66.5)Sol/s 137(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/34%] 33.78 I/s 67.7(67.2)Sol/s 138(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m11s|15:11:52 29/08/2019] 135(133.8)Sol/s 274(271.7)W
0>GTX 1080 ` 100% [54шC/29%] 33.45 I/s 67.0(66.5)Sol/s 135(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/32%] 33.78 I/s 67.9(67.3)Sol/s 139(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m21s|15:12:02 29/08/2019] 135(133.8)Sol/s 271(271.6)W
0>GTX 1080 ` 100% [54шC/30%] 33.45 I/s 66.9(66.5)Sol/s 135(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/33%] 33.78 I/s 68.1(67.3)Sol/s 137(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m31s|15:12:12 29/08/2019] 135(133.8)Sol/s 179(268.6)W
0>GTX 1080 ` 100% [49шC/22%] 33.45 I/s 66.9(66.5)Sol/s 89(132.9)W clk=1607MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [50шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 90(134.6)W clk=1670MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m41s|15:12:22 29/08/2019] 135(133.8)Sol/s 97(264.4)W
0>GTX 1080 ` 100% [48шC/10%] 33.45 I/s 66.9(66.5)Sol/s 48(132.8)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [48шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 49(134.5)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h10m51s|15:12:32 29/08/2019] 135(133.8)Sol/s 56(260.2)W
0>GTX 1080 ` 100% [46шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 28(132.7)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [46шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 28(134.5)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m01s|15:12:42 29/08/2019] 135(133.8)Sol/s 36(256.2)W
0>GTX 1080 ` 100% [45шC/16%] 33.45 I/s 66.9(66.5)Sol/s 18(132.7)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [45шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 18(134.4)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m11s|15:12:52 29/08/2019] 135(133.8)Sol/s 27(252.3)W
0>GTX 1080 ` 100% [44шC/21%] 33.45 I/s 66.9(66.5)Sol/s 12(132.6)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [43шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 15(134.3)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m21s|15:13:02 29/08/2019] 135(133.8)Sol/s 23(248.4)W
0>GTX 1080 ` 100% [43шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 10(132.5)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [42шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 13(134.2)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m31s|15:13:12 29/08/2019] 135(133.8)Sol/s 18(244.5)W
0>GTX 1080 ` 100% [42шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 8(132.4)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [41шC/25%] 33.78 I/s 68.1(67.3)Sol/s 10(134.1)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m41s|15:13:22 29/08/2019] 135(133.8)Sol/s 16(240.7)W
0>GTX 1080 ` 100% [42шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 8(132.3)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [40шC/27%] 33.78 I/s 68.1(67.3)Sol/s 9(134.0)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m51s|15:13:32 29/08/2019] 135(133.8)Sol/s 16(237.0)W
0>GTX 1080 ` 100% [41шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 7(132.2)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [39шC/11%] 33.78 I/s 68.1(67.3)Sol/s 9(133.9)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m01s|15:13:42 29/08/2019] 135(133.8)Sol/s 15(233.3)W
0>GTX 1080 ` 100% [40шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 7(132.1)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [38шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 8(133.8)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m11s|15:13:52 29/08/2019] 135(133.8)Sol/s 15(229.7)W
0>GTX 1080 ` 100% [39шC/20%] 33.45 I/s 66.9(66.5)Sol/s 7(132.0)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [37шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 8(133.8)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m21s|15:14:02 29/08/2019] 123(133.6)Sol/s 14(226.1)W
0>GTX 1080 ` 100% [38шC/22%] 30.47 I/s 61.0(66.4)Sol/s 7(132.0)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [36шC/ 0%] 30.72 I/s 61.9(67.2)Sol/s 7(133.7)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m31s|15:14:12 29/08/2019] 125(133.6)Sol/s 139(226.7)W
0>GTX 1080 ` 100% [44шC/ 0%] 30.76 I/s 61.9(66.4)Sol/s 69(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [41шC/ 0%] 31.02 I/s 62.5(67.2)Sol/s 70(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h12m41s|15:14:22 29/08/2019] 125(133.6)Sol/s 205(227.5)W
0>GTX 1080 ` 100% [46шC/ 0%] 31.02 I/s 61.9(66.4)Sol/s 100(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [42шC/ 0%] 31.29 I/s 63.0(67.2)Sol/s 105(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h12m51s|15:14:32 29/08/2019] 126(133.6)Sol/s 237(228.2)W
0>GTX 1080 ` 100% [47шC/ 0%] 31.25 I/s 62.7(66.4)Sol/s 119(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [44шC/ 0%] 31.54 I/s 63.4(67.2)Sol/s 118(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m01s|15:14:42 29/08/2019] 127(133.6)Sol/s 254(228.9)W
0>GTX 1080 ` 100% [49шC/23%] 31.47 I/s 63.2(66.4)Sol/s 129(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [45шC/25%] 31.76 I/s 63.7(67.2)Sol/s 125(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m11s|15:14:52 29/08/2019] 127(133.6)Sol/s 264(229.6)W
0>GTX 1080 ` 100% [51шC/11%] 31.66 I/s 63.3(66.4)Sol/s 132(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [47шC/25%] 31.96 I/s 64.2(67.2)Sol/s 132(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m21s|15:15:03 29/08/2019] 128(133.6)Sol/s 268(230.3)W
0>GTX 1080 ` 100% [52шC/19%] 31.83 I/s 63.0(66.4)Sol/s 133(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [48шC/26%] 32.14 I/s 64.7(67.2)Sol/s 135(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50

BigHarryArmsi

newbie

Activity: 137

Merit: 0

Thanks for all the help!
[/quote]
Hi BigHarryArmsi,
the oc1 may get you a performance improvement, but this depends on your settings. It is good to try it and check which is best for your configuration.
You can add to the command line --oc1, or in your case bat file:

Code:

:loop
.\miniZ.exe --url=ssl://1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334 --oc1
timeout /t 5
goto loop

Regarding the red percentages, it seems that you had a few invalid shares and likely in the beginning. Did the red percentage turned green? Or at least is the percentage converging to 100?
This can happen, but it should be sporadic. Do let us know if it happens often.
Cheers
[/quote]

Both oc1 and oc2 slowed my hashing. OC1 especially, so I am running without either.
5)6gb MSI 1060s 65%-140-400 are ~20, MSI 1080 70%-135-350 is ~40
146 Sols at ~530w

And yes, the red %s are going away after a couple of hours, first going to dark pink then orange then to green. Expecting them all to go green before long. I had never seen reds before with miniZ on 144_5 so it was unnerving to see a sea of red!

Thanks again for the help. Will be tuning up another rig tomorrow!

miniZ

member

Activity: 690

Merit: 17

Quote from: BigHarryArmsi on August 28, 2019, 07:00:32 PM

Hi, miniZ

I see a lot of chatter about OC settings. (OC1 and OC2) Where do I put that setting. In my bat file? Kinda slow here, I'm thinking I'm missing something. Then a bunch of red percentages after a couple of minutes!
6gb MSI 1060s ~20 Sols pwr 75% 100 and 200 clocks
MSI 1080 ~35 Sols 75% 100 and 200 clocks
Running Win10 Driver version 430

Thanks for all the help!

Hi BigHarryArmsi,
the oc1 may get you a performance improvement, but this depends on your settings. It is good to try it and check which is best for your configuration.
You can add to the command line --oc1, or in your case bat file:

Code:

:loop
.\miniZ.exe --url=ssl://1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334 --oc1
timeout /t 5
goto loop

Regarding the red percentages, it seems that you had a few invalid shares and likely in the beginning. Did the red percentage turned green? Or at least is the percentage converging to 100?
This can happen, but it should be sporadic. Do let us know if it happens often.
Cheers

BigHarryArmsi

newbie

Activity: 137

Merit: 0

Hi, miniZ

I see a lot of chatter about OC settings. (OC1 and OC2) Where do I put that setting. In my bat file? Kinda slow here, I'm thinking I'm missing something. Then a bunch of red percentages after a couple of minutes!
6gb MSI 1060s ~20 Sols pwr 75% 100 and 200 clocks
MSI 1080 ~35 Sols 75% 100 and 200 clocks
Running Win10 Driver version 430

Thanks for all the help!

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