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

Hi everyone,

A new version miniZ v1.6v is out with added support for the new Beam algorithm - BeamHash III (144,5-siphash) - a new algorithm introduced for Beam mining in the upcoming Beam hard fork at block height 777777, expected on 28 June 2020.

miniZ will automatically switch for the new algorithm. You can mine Beam the way you have been doing currently.

We will keep working to make miniZ better. Thank you all for your feedback!

Download miniZ v1.6v here.


Changelog:
* Added support for BeamHash III. (Hashrate below)
* Fixed --show-mode option that was only showing in combination with other options.
* Included another low memory mode for 1060 3GB on ZEL. (running with --oc2)
* Completely reworked the --ocX mechanism.
* Changed kernel calls for 150,5. Let us know if it improves your driver CPU usage.
* Better default kernels for GTX1070, on stock settings, for all algorithms.

Equihash - BeamHash III:
* GTX 1050 2GB ~3.3 Sol/s
* GTX 1050 Ti 4GB ~  6.6 Sol/s
* GTX 1060 3GB ~ 8.2 Sol/s
* GTX 1660 Ti 8GB ~ 15.7 Sol/s
* GTX 1070 8GB ~ 17.4 Sol/s
* GTX 1070 Ti 8GB ~ 19.6 Sol/s
* GTX 1080 8GB ~ 19.0 Sol/s
* GTX 1080 Ti 11GB ~ 28.3 Sol/s
* RTX 2070 8GB ~ 23.2 Sol/s


Few notes:

* When adjusting your GPUs settings do not forget to check if your GPU has oc1/oc2. If so it may boost your performance a little.
  These refer to specific kernels/modes that will run in your GPU, kernels that with we found to be good when overclocking the cards. Alternatively, you can also use an option for automatic tunning of the best kernel for your GPU and OC settings --ocX, now available in all algorithms.
  For updated information read the specific topic on FAQ page.
* On Download page you can find Cuda 10 version (Linux and Windows).


For additional information check our Usage or FAQ pages.

We wish you a fast and friendly mining experience!

and
to offer a great pool for your devfee -

https://minebeam.raskul.com (USA)
or
https://pool.raskul.com (UK)

Wonderful.

Hi MrPlus,
We are currently taking care of the last details. The release will be out today....within the next hour or so.
Cheers

Hi Ziv1,
Thank you for the information.
The mode 0 takes almost all the memory of the GPU, and there is nothing left for GPUz.
In the new version (1.6v, will be out today) the default kernel is a tiny smaller (few MB). We hope that this size decrease will be enough to make your GPUs run with newest kernel.
However, we managed to recover the older kernel that you can run just by adding --oc2 (or --mode 16). But remember that this one is way smaller and it does not perform as good as the kernel in recent versions.
We'll try to decrease the best kernel a bit more without compromising performance, in future versions.
Let us know if this solves your issue.
Cheers

Hi,

Any info on coming Beam fork support (june 28th)

Hello miniZ.
W 7 125.4 ZEL 1060-3GB
The main version that I use is 1.5t.
When using it, there are no problems with the joint launch of control and monitoring of video cards (in the operating load mode).
Version 1.5u2 is being tested.
Monitoring does not work (in operating mode) .Try
switch to monitoring settings in GPUZ.
I associate this with the increased volume of video memory
maps (3067mv).
Can one hope that in new versions this value will decrease to 2692mv (as in version 1.5t)?

Hi somaton,
Nice that you managed to add the two pools and to use miniZ from the config file.

Regarding the messages, when miniZ cannot connect to the first mining pool (the first you define, in case there two or more pools defined by the  user) it will start saying that it cannot connect.
If after a few quick attempts it cannot connect then it will connect to the second pool. However, it keeps trying to connect to the first pool.

If the miner cannot connect to any mining pool it will keep looping through the list of pools until it can connect somewhere, it still tries to reconnect to the first pool all the time.

The No error: connect message, just means that there was a failed attempt to connect, in this case because the pool is down.

The miner does not know when the pool will be back up, so it keeps trying, it does not matter for how long it was down.

Hope this helps to clarify some doubts. We'll have a look and review the messages in future releases.
Thanks for the feedback!
Cheers

Hi MineOrDie,
We are not aware of any regressions on 1060 3GB.
What is the algo that you are mining?

Could you help us understand  what is happening by giving some more information?

If you paste here the start of the log (until it starts mining), for both versions, for example, this may be helpful.

Thank you for the feedback!
Cheers

Hi  Ziv1,
sorry for taking a bit longer than usual to reply, we've been busy with Beam fork.

On Windows, mode 0 for ZEL mining needs slight less than 3GB (it is a bit tight).  This also depends on how much is the operative system overhead.

If miniZ starts mining then the memory is not the problem.

Is miniZ not starting anymore? The last time you showed the log it was looking fine despite the fact that it was not submitting  the shares.
Cheers

Last two days when zergpool and zpool are not working well because of ddos atacks, i have tested miniz capability to switch between main and backup pools - need more work with error and info messages. Every 30 secs i see this: No error: connect - what problem with connect or it cant connect anywhere? I have to check gpu temperatures to see is it mining at all or is miner really not connected to any pool or what is going on? Every ~1,5 min i see this: Cannot connect to equihash192.mine.zergpool.com pool, reconnect in 5 seconds! Why reconnect in 5 seconds if it is down for many hours? Why then i see this error every 1,5 min if reconnect attempt is every 5 secs? This part of miner still need some work, too many weird messages. T-rex is very good example how it can be.

I tend to get 15 sols less on my 1060 3GB rigs compared to 1.5t2.
Running 1.5u2, Windows 8.1 and the latest drivers.

Mine ZEL-125.4  mode 0.
How much video memory is required for such mining.

miniZ: Got two pools working through one .conf file, thank you for all your suggestions!

Hi topteam,
The cuda 10 version of miniZ works fine with GTX GPUs, you just need to update the Nvidia driver. (NVIDIA 410.48 driver or later)
The latest should be fine.
We added Cuda 8 Linux version to Download page, but we suggest you to update the Nvidia driver.
Cheers

yea ubuntu 16 and driver 396.82
reason - only GTX cards

Hi topteam,
From version t3 we announced that we would stop supporting Cuda 8.
If you really need it, we can add it for now, but you should consider updating your drivers do you have a reason to not do so?
(You still use Linux ,right?)
Cheers

Hi Kringel,
Sorry for the confusion. We understand your frustration.
We'll do our best to improve this and will also optimise the default kernels for the 1070, in all agos.
Thank you for your feedback.
Cheers

Hi Ziv1,
Thank you for your reply.

Kernels 0 and 14 should work with your GPU on Windows 7 (ZEL).

If your GPUs are unstable do not use ocX option, just run try directly --mode 0 or --mode 14.

If miniZ is still unstable you may need to adjust your oc settings a little bit, maybe decreasing slightly the core clock.

You may also try to run only one gpu at a time to understand which one is triggering the instability.

Hope this will help.
Cheers

can't find cuda 8 build