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

Same problem with a 3080 seems to cap at 2 or less temps do not seem to increase either



[ 0d 0h 0m04s] 0>RTX 3080 ` 100% [41°C/53%] 0.93 I/s 1.9(1.9)Sol/s  97( 96.7)W clk=1965MHz mclk=9251MHz Sol/W=0.02
[ 0d 0h 0m10s] 0>RTX 3080 ` 100% [43°C/53%] 0.93 I/s 1.9(1.9)Sol/s 146(145.8)W clk=1965MHz mclk=9251MHz Sol/W=0.01
[ 0d 0h 0m20s] 0>RTX 3080 ` 100% [45°C/53%] 0.92 I/s 1.8(1.8)Sol/s 150(149.6)W clk=1965MHz mclk=9251MHz Sol/W=0.01

RTX 3000 still need more work:

[ 0d 0h14m31s|05:06:17 05/11/2020] S:  0/1  2( 1.6)Sol/s  79( 74.4)W [beamv3.eu.nicehash.com,Beam-PoW]- 113ms
 0>RTX 3070    [11] 0.00% [42°C/30%] 0.38 I/s 2.3(1.6)Sol/s  79( 74.4)W clk=1995MHz mclk=7000MHz Sol/W=0.02

Hi sihuoyu,

Thank you for the feedback.

It is best to use Cuda 10 for all. You will only need to have Nvidia driver version >=411.31.
See Table 2 @ https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html

We are not sure to have properly understand your statement. RTX 20XX and GTX 16XX GPUs need Cuda10 (they are Turing-based GPUs).
“CUDA 10.0 adds support for the Turing architecture (compute_75 and sm_75).” (in Release notes: https://docs.nvidia.com/cuda/archive/10.0/cuda-toolkit-release-notes/index.html).
You can also read some information @ https://en.wikipedia.org/wiki/Turing_(microarchitecture)

The best is to make sure you update the driver to >=411.31 version and use miniZ Cuda 10, even for the GTX 950/750 this should be the best.
In any case we’ll have a look at this issue and work on improvements of intensity option for the next version.

We are not sure how can we help further at the moment, let us know if you have any other suggestions.
Cheers
ps: dev. fee is 2% of mining time.

Hi sihuoyu,

You can find miniZ v1.6w3 with a fix for intensity option, for 210,9. Download here: https://miniz.ch/download-beta/
Let us know if it is working for you, we make this available as beta because it was not deeply tested.

For RTX 20XX and GTX 16XX you’ll need to use Cuda 10 version.

Cuda 11 will only be necessary for RTX 30XX series.

Cuda 8 is no longer supported but we updated the files too. Soon we’ll stop updating these. It is best to move to CUDA 10.

Hope this helps. 🙂
Cheers

Hi sihuoyu,
If you need to mine 210,9 we’ll see if we can provide a fix for this very soon. The intensity option seems to work much better in other algos.

Could you let us know which OS and which CUDA version are you using?
Cheers
ps: We've also answered to your message on miniZ website.

Hi sihuoyu,
It looks that you’re using the option well.
We’ll have a look. It seems that the intensity option is not optimised for AION. It should be fixed in the next version.

At the moment, you can try a less optimised kernel that may free some GPU resources.
We’re not sure this will work but it is worth to try. Use --mode=[0-9], and do not use -i option now.

Currently we are also working on improvements for 210,9. 🙂

Thanks for using miniZ!
Cheers

90 Sol Equihash 192,7 with 3080 at 255 W Lovely... Great JOB
[/quote]

Hi jgonzi, 18-Terahash,
We'll keep improving miniZ
Thanks a lot for the feedback, it is very much appreciated!
Cheers

With the new version it looks ok. W10, G3930, 6x 1080ti cpu load 100%, new version 70%. Great

90 Sol Equihash 192,7 with 3080 at 255 W Lovely... Great JOB

Hi everyone,

Thank you for your patience and for using miniZ miner!

A new miniZ v1.6w2 version is out with major improvements in 192,7 algorithm - Ycash, Zero, Vidulum, Zclassic, SafeCoin...

Please find miniZ v1.6w2 version @ Download page.
 
Changelog:

 * 192,7 major improvements: ~2-11% depending on GPU. Turing GPUs, and 1050 Ti, have the largest improvements.
 * Reduced invalid shares on 192,7.
 * Added 2GB kernel for 192,7 (Linux/Windows7).
 * Added 3GB kernel for 192,7 (Windows 10).
 * Added 2GB kernel for 144,5s (beamhash3) (Windows7).
 * Added experimental support for Ampere GPUs. (Use Cuda 11.1 version.)
 
For the Ampere architectures (RTX 30 series) you need to use Cuda 11.1 versions, and have installed:
 * NVIDIA 455.23 driver or later, for version compiled with cuda 11.1 (Linux).
 * NVIDIA 456.38 driver or later, for version compiled with cuda 11.1 (Windows).
 
Remember to try --oc1--oc2--ocX options for optimum performance.
 
Download miniZ version v1.6w2 here.

For additional information check our Usage or FAQ pages.

Follow us
On Twitter

Happy miniZ mining!

Hi jgonzi,
Thank you for your kind words.
You can find the new miniZ version v1.6w2 with major improvements for Equihash 192,7.

Also, you'll be able to find a version for the RTX 30 series. It is still experimental so all the feedback is very much welcome.

If you happen to mine other algos (besides 192,7) we would appreciate the feedback too.

Cheers

Always like Pro!!! Many thanks man... It has been always my preferred miner, lot more improved than the others, and always more hash than calculators. It is a petty only for Nvidia...  jeje...

As soon as it is released I will post results if that helps♧

************ miniZ v1.6w ************
Algo:           EQ[96,5]
Pool#0:         user[*****************************************]
                server[equihash96.eu.mine.zpool.ca] port[2196] ssl[no] pers[auto]
Telemetry:      [http://localhost:4004]
Optimisation:   ocX[0]
Temp. limit:    [90°C]
miniZ<96,5>[02:0:00:5167]: Selecting GPU#0[0] GeForce GTX 1660 SUPER
[ 0d 0h 0m05s] S:  0/0 0>GTX 1660 SUPER ` 100% [45°C/33%] 1012250 I/s 2019438.8(2019438.8)Sol/s  32( 32.2)W clk=1530MHz mclk=7610MHz Sol/W=62756.42 [equihash96.eu.mine.zpool.ca,GLT-Mars]- 96ms
[ 0d 0h 0m10s] S:  0/0 0>GTX 1660 SUPER ` 100% [47°C/33%] 427275 I/s 852413.6(852413.6)Sol/s  51( 50.7)W clk=1530MHz mclk=7610MHz Sol/W=16816.74 [equihash96.eu.mine.zpool.ca,GLT-Mars]- 96ms
[ 0d 0h 0m20s] S:  1/0 0>GTX 1660 SUPER ` 100% [48°C/33%]*114516 I/s 228427.6(228427.6)Sol/s  52( 51.9)W clk=1530MHz mclk=7610MHz Sol/W=4399.64 [equihash96.eu.mine.zpool.ca,GLT-Mars]- 95ms (100.0%) (0.0%)
[ 0d 0h 0m30s] S:  1/0 0>GTX 1660 SUPER ` 100% [48°C/33%] 54863 I/s 109428.4(109428.4)Sol/s  52( 52.4)W clk=1530MHz mclk=7610MHz Sol/W=2086.80 [equihash96.eu.mine.zpool.ca,GLT-Mars]- 95ms (100.0%) (0.0%)

miniZ v1.6w is reporting insane high hashrate when beginning to mine Equihash 96.5.
This leads to incorrect benchmark results.
Other algos - I just tested E1254 - do not show this issue.

Hi jgonzi,
Thank you for your message, for remembering us that we need to release a CUDA 11 version.

We are finalising a new miniZ version, it should be out soon.
We will add test support for for RTX 3XXX, we expect these GPUs to perform well but there is still room for improvements.

You'll be glad to know that improvements to 192,7 are also on the way.
Cheers

Number of CUDA[10.0] devices found: 1
Algo:           EQ[192,7]
Pool#0:         user[1MgDZZcgeTWsCc2ZK2vDw8bhGwvZLwuBvC]
                server[equihash192.eu.mine.zergpool.com] port[2144] ssl[no] pers[auto]
Telemetry:      [http://localhost:20000]
Temp. limit:    [90°C]
miniZ<192,7>[06:0:00:9791]: Selecting GPU#0[0] GeForce RTX 3080
[FATAL  ] Cannot load deviceZ code.
[INFO   ] Disconnecting from equihash192.eu.mine.zergpool.com
[INFO   ]equihash192.eu.mine.zergpool.com Stopping miner

Waiting for the update to prove with the news RTX...

Hi bourbonmorning,
We managed to shrink it a bit. Soon you'll be able to mine BeamHashIII with your GTX1050 2GB under Windows 7, it may be able to get around 4 Sol/s
We have been working on a new miniZ version, with additional improvements, we estimate that it will take only a couple of days to release.
Cheers

Hi BigHarryArmsi,
Have you managed to find a nice and stable configuration for your rig? Also, did you find time to check if v3 was working with your setup?
We have been working on a new version, hopefully it will deal with your issue. We expect to release it soon.
Cheers

Any news?

Thanks for the kind words, miniZ!
I experimented some more to no avail. Any change in OC setting and hash is diminished and going below 81% power (~920 mv) brings on a crash. Rock steady for a couple of days now at 43.2 hashes @ 241 watts. Zed core clock and -500 memory. Strange settings it seems but any changes diminish or crash. This is a Win10 rig, nothing fancy. 2/850w power supplies Celeron processor 4gb ram. Comparing to others I have seen it's good hashes and meh power, but strange settings to get there, eh? Thanks again for help and kind words.
 

Hi BigHarryArmsi,

Thank you for your message, nice to hear from you again.

We suggest you to try half of -500 MHz on memory clock, something like -250 MHz. -500 MHz might be to much. Possibly you can even add something to core clock.
You can find some values and OCs for BeamHashIII in our website here maybe they can be applied to your 2080Ti. (We report OC values that we set in Linux. Memory clock in MSI Afterburner should be half of the indicated values.)
 
miniZ v2 was removed because of some things that needed to be fixed, you can try v3 it should be the same but without the issues in v2. In any case we think that you may need to change mem clock.
 
We will create a kernel for 2080Ti that uses a different technique, it should perform equally well and it may cope better with your OC settings.
 
Let us know if you managed to make it work.

Cheers