Pages:
Author

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

jr. member
Activity: 75
Merit: 1
Hey,

ZEL will have an upcoming algo change to ther unique algo, can you maybe reach out to them, offer your help and be the one who will provide the most optimized miner when they release their upgraded network?

Also n5 gives me a bit lower hashrate on 144,5 compared to n4.
member
Activity: 690
Merit: 17
What does the —oc1 and —oc2 do? I’m mining Beam on Hiveos with 1080Ti’s. Allready applied oc and pl within hiveos. Do I still use -oc1 or —oc2?

Love miniz by the way 💪
Hi Porrit,
The --oc1 and the --oc2, just help miniZ to tune the algo according to
your overclock settings.
You first you should do the overclock/power limit like you usually do,
and only then try to start miniZ with --oc1 or --oc2 to see if you get an extra boost.
Thank you for using miniZ. Smiley
Cheers

Thanks, it does not make any difference for me. Oc1 gives worse hash and oc2 the same hash as none used.
Hi Porrit,
--oc1/2 may not improve performance, it really depends on the OCs and power limit you are using. This option is a way to make the miner more flexible and adaptable to each rig configuration.
Cheers
member
Activity: 690
Merit: 17
* Better mode detection 3GB cards. (150,5)

Can you give more details? Does this mean automatic --mode=3 even when flag not included in command line?
Hi ltxminer,
That was the ideia... did it work for you? Smiley
Cheers


It did not.

My rig card #0 is 6gb, the rest is 3gb
Maybe that is the problem for your auto setting
Hi ltxminer,
When you use --mode=3, the miner will apply this mode to all GPUs. This includes the 1060 6GB that will run slower since this (very likely) is  not the optimal mode for this GPU.
You can try running miniZ with --mode=3 --mode0 4 or --mode=3 --mode0 8, this will set mode=3 for all GPUs except for the GPU#0.
Sorry about the complicated settings. --mode is still an experimental setting, and we are going to try to improve automatic detection for the next release.
Cheers
newbie
Activity: 19
Merit: 0
What does the —oc1 and —oc2 do? I’m mining Beam on Hiveos with 1080Ti’s. Allready applied oc and pl within hiveos. Do I still use -oc1 or —oc2?

Love miniz by the way 💪
Hi Porrit,
The --oc1 and the --oc2, just help miniZ to tune the algo according to
your overclock settings.
You first you should do the overclock/power limit like you usually do,
and only then try to start miniZ with --oc1 or --oc2 to see if you get an extra boost.
Thank you for using miniZ. Smiley
Cheers

Thanks, it does not make any difference for me. Oc1 gives worse hash and oc2 the same hash as none used.
newbie
Activity: 14
Merit: 0
* Better mode detection 3GB cards. (150,5)

Can you give more details? Does this mean automatic --mode=3 even when flag not included in command line?
Hi ltxminer,
That was the ideia... did it work for you? Smiley
Cheers


It did not.

My rig card #0 is 6gb, the rest is 3gb
Maybe that is the problem for your auto setting
member
Activity: 690
Merit: 17
What does the —oc1 and —oc2 do? I’m mining Beam on Hiveos with 1080Ti’s. Allready applied oc and pl within hiveos. Do I still use -oc1 or —oc2?

Love miniz by the way 💪
Hi Porrit,
The --oc1 and the --oc2, just help miniZ to tune the algo according to
your overclock settings.
You first you should do the overclock/power limit like you usually do,
and only then try to start miniZ with --oc1 or --oc2 to see if you get an extra boost.
Thank you for using miniZ. Smiley
Cheers
member
Activity: 690
Merit: 17
* Better mode detection 3GB cards. (150,5)

Can you give more details? Does this mean automatic --mode=3 even when flag not included in command line?
Hi ltxminer,
That was the ideia... did it work for you? Smiley
Cheers
newbie
Activity: 19
Merit: 0
What does the —oc1 and —oc2 do? I’m mining Beam on Hiveos with 1080Ti’s. Allready applied oc and pl within hiveos. Do I still use -oc1 or —oc2?

Love miniz by the way 💪
newbie
Activity: 14
Merit: 0
* Better mode detection 3GB cards. (150,5)

Can you give more details? Does this mean automatic --mode=3 even when flag not included in command line?
member
Activity: 690
Merit: 17
Hi everyone,

Thanks for your feedback!
We made available new files for both Windows and Linux, miniZ v1.3n5 with a few more fixes.  Smiley

* Improved stale shares.
* Fixed GTX 1060 settings without oc1/2. (144,5)
* Better mode detection 3GB cards. (150,5)
* Fixed templimit in configuration file.

You can find the miniZ v1.3n5 on our website https://miniz.ch/download/

For those who use Hive OS check here.

Thank you for using miniZ!
Cheers
member
Activity: 690
Merit: 17
miniZ v1.3n4 "beam" W10  rig 6x1080ti   rig 6x1060 6GB stable nice work thanks "better than gminer, who mysteriously released the update"
Hi stzcze,
Thank you for your message.
It is great to know that our work is appreciated!
We have just released v1.3n5 with a few fixes.
Cheers
jr. member
Activity: 109
Merit: 1
miniZ v1.3n4 "beam" W10  rig 6x1080ti   rig 6x1060 6GB stable nice work thanks "better than gminer, who mysteriously released the update"
member
Activity: 690
Merit: 17
Thanks for explanation. Looks like you are right - most rejects are shown in red (stale). In this pic starting from 1.5 i was testing other miner with same algo 150,5, that is why reject rate is much lower, but 29.4 is what i had when i was testing first revision of n (does not look very good, many rejects in orange too). 30.4 i was runnig n2, n3 versions and graphic is much better.

Hi somaton,
Thank you for sharing this information.
The stale shares may look a bit high in your case. We are looking into it to further check if we can improve this.
Cheers
jr. member
Activity: 212
Merit: 6
Thanks for explanation. Looks like you are right - most rejects are shown in red (stale). In this pic starting from 1.5 i was testing other miner with same algo 150,5, that is why reject rate is much lower, but 29.4 is what i had when i was testing first revision of n (does not look very good, many rejects in orange too). 30.4 i was runnig n2, n3 versions and graphic is much better.

member
Activity: 690
Merit: 17
I see same story on my rigs, when i'm using other 150,5 miner (to compare with n3) there is almost no rejects when checking nicehash site, but with n3 % of rejects is always higher.
Hi somaton,
When you have a stale share you just get a yellow star on the miner console, the efficiency only accounts for the number of accepted and invalid shares. To see the other shares you have to look at the telemetry, it would be the middle value on the shares column.

We can see that nicehash, after sending a new job, does not accept submissions from previous jobs. Some pools still accept it, others like nicehash do not. We've tested and managed to see that when the miner receives a new job, just before submiting a solution from a previous work, this results in a rejected share from that submission.

(edit) If we remove this submission the miners will not gain anything from it. You'll get better efficiency on the pool, but you will earn the same (since nicehash does not accept it anyway). As we said before, some pools still accept these submissions.

Can you let us know what reason for rejection does nicehash report. You can check your graphic. It can say rejected (target), rejected (stale), rejected (duplicate)...
Cheers
jr. member
Activity: 212
Merit: 6
I see same story on my rigs, when i'm using other 150,5 miner (to compare with n3) there is almost no rejects when checking nicehash site, but with n3 % of rejects is always higher.
member
Activity: 690
Merit: 17
Hi everyone,
Thanks a lot for your feedback.

We made available miniZ v1.3n4 with a few fixes, for you to download.

* Fixed ssl connection fault.
* Improved CPU load.
* Display NA for temperature when not available.
* Improved 1080 hashrate with --oc1.

You can download here https://miniz.ch/download/

For those who use Hive OS there is a new link for you:
http://miniz.ch/hiveos/miniZ-1.3n4.tar.gz

Thank you for helping us improve miniZ.
Cheers
newbie
Activity: 157
Merit: 0
I see rejects on pool side, but no one reject on miner
Can you check (beam, pool btc.com)?
Code:
[ 0d19h10m36s] S:4627/0 288(287.8)Sol/s 1639(1628.4)W [eu-beam.ss.btc.com,Beam-PoW]- 44ms (98.0%) (2.0%)
https://imgur.com/kiV83Pk

Hi topteam,
thank you for reporting this.
It may be the case that the server is not reporting invalid shares, or that these are stale shares and in this case they show up in telemetry.
Just to confirm, are you are using miniZ v1.3n3?
Cheers
Yes, miniZ v1.3n3
member
Activity: 690
Merit: 17
I see rejects on pool side, but no one reject on miner
Can you check (beam, pool btc.com)?
Code:
[ 0d19h10m36s] S:4627/0 288(287.8)Sol/s 1639(1628.4)W [eu-beam.ss.btc.com,Beam-PoW]- 44ms (98.0%) (2.0%)


Hi topteam,
thank you for reporting this.
It may be the case that the server is not reporting invalid shares, or that these are stale shares and in this case they show up in telemetry.
Just to confirm, are you are using miniZ v1.3n3?
Cheers
newbie
Activity: 157
Merit: 0
I see rejects on pool side, but no one reject on miner
Can you check (beam, pool btc.com)?
Code:
[ 0d19h10m36s] S:4627/0 288(287.8)Sol/s 1639(1628.4)W [eu-beam.ss.btc.com,Beam-PoW]- 44ms (98.0%) (2.0%)
https://imgur.com/kiV83Pk
Pages:
Jump to: