miniZv2.4d Equihash144,5 125,4 210,9 150,5 192,7 Beam ProgPoW Ethash CFX KLS PYI

[miniZ]

Hi webgkv,

I am not very familiar with power shell, but I think that miniZ does not like your getstat request.

Try instead of:

Code:

$Message = @{id = 1; method = "getstat"} | ConvertTo-Json -Compress

to use:

Code:

$Message = '{"id":"0", "method":"getstat"}'

not as pretty as what you had before, but it should do the trick.
(Also feel free to send us a private message if you think it would be useful)


Hi 1ncehost,

  Sorry for the inconvenience... we try to make sure that there are no regressions on new releases, but there are so many cards/overclock setting combinations that this might happend.
Which cards do you have on your rigs and which OS are you using? The changes from i+ to i++ are minimal, it would be interesting to understand what caused the problem. Thanks for your feedback!

Cheers and happy mining!

[webgkv]

Hi webgkv,

I am not very familiar with power shell, but I think that miniZ does not like your getstat request.

Try instead of:

Code:

$Message = @{id = 1; method = "getstat"} | ConvertTo-Json -Compress

to use:

Code:

$Message = '{"id":"0", "method":"getstat"}'

Now it works great, thanks for the help!

[rekoe]

Very fast. Thanks to the developers.

[supervitek]

Hi MiniZ,

Your miner is closing with an error, any idea where can I check what kind of error is happening?

I tried to use it on 2 1050 Ti cards and it is always closing after 20-30 mins. I updated the system to a last driver - no success. I used 9.2 and 8 versions - same problem.

Also if I set --intensity 80 (any intensity) the miners stuck like this:

https://i.ibb.co/qMhQSrF/miniz-stuck-on-intensity.png

Thank you!

P.S. This is how it stuck:

https://i.ibb.co/hczrFqc/miniz-error-stop.png

[fistsofgod]

  0>GTX 1070       [52°C/61%]
  1>GTX 1070       [45°C/55%]
  2>GTX 1070       [46°C/55%]

with the space between card name and temp/fan could you put in per gpu rejected share number?

[1ncehost]

Hi 1ncehost,

  Sorry for the inconvenience... we try to make sure that there are no regressions on new releases, but there are so many cards/overclock setting combinations that this might happend.
Which cards do you have on your rigs and which OS are you using? The changes from i+ to i++ are minimal, it would be interesting to understand what caused the problem. Thanks for your feedback!

Cheers and happy mining!

I have GTX 1060s running at half power and stock clocks. H was the fastest build on them. "I" ran about 5% slower and i++ ran slower still. The time sample size for i and i++ could be small enough to not be meaningful (I didn't run I for long), but the sample size between H and I++ was meaningful. H was considerably faster than I++.

[supervitek]

Hi 1ncehost,

  Sorry for the inconvenience... we try to make sure that there are no regressions on new releases, but there are so many cards/overclock setting combinations that this might happend.
Which cards do you have on your rigs and which OS are you using? The changes from i+ to i++ are minimal, it would be interesting to understand what caused the problem. Thanks for your feedback!

Cheers and happy mining!

I have GTX 1060s running at half power and stock clocks. H was the fastest build on them. "I" ran about 5% slower and i++ ran slower still. The time sample size for i and i++ could be small enough to not be meaningful (I didn't run I for long), but the sample size between H and I++ was meaningful. H was considerably faster than I++.

That is interesting, one of my card in a RIG is 1060 3 Gb and "I++" is faster than "H" (I tried H cause I have non stop closing of the program with no error message in about 20 mins - 1 hour).

[lost2217]

msi armor 2070 63-65  Sol/s

[zorkilion]

I like your miner. Testing now 

[alucard20724]

will you be creating a windows cuda 10 version?

[fistsofgod]

192,7

[miniZ]

  0>GTX 1070       [52°C/61%]
  1>GTX 1070       [45°C/55%]
  2>GTX 1070       [46°C/55%]

with the space between card name and temp/fan could you put in per gpu rejected share number?

Hi fistsofgod,
we'll do that for the next version.

192,7

We are working on improving the 144,5, but we plan to work on that in a near future

Cheers

[miniZ]

Very fast. Thanks to the developers.

Hi rekoe,
thank you!

I like your miner. Testing now 

Hi zorkilion,
thanks. Then share with us how it went.

msi armor 2070 63-65  Sol/s

Hi lost2217,
thank you for letting us know! Feedback on RTX is very much appreciated!

[miniZ]

I have GTX 1060s running at half power and stock clocks. H was the fastest build on them. "I" ran about 5% slower and i++ ran slower still. The time sample size for i and i++ could be small enough to not be meaningful (I didn't run I for long), but the sample size between H and I++ was meaningful. H was considerably faster than I++.

That is interesting, one of my card in a RIG is 1060 3 Gb and "I++" is faster than "H" (I tried H cause I have non stop closing of the program with no error message in about 20 mins - 1 hour).

I have GTX 1060s running at half power and stock clocks. H was the fastest build on them. "I" ran about 5% slower and i++ ran slower still. The time sample size for i and i++ could be small enough to not be meaningful (I didn't run I for long), but the sample size between H and I++ was meaningful. H was considerably faster than I++.

Hi 1ncehost, supervitek,
Thanks for reporting this. That is interesting. We tested on a 1060 3Gb, v1.0i++ (https://miniz.ch/features/) is significantly faster than v1.0h (https://miniz.ch/2018/11/30/my-sol-s/).
There is some variability since these values depend on brand, temperature, stock/OC settings...
We are working on a new version that should be faster than both v1.0h and v1.0h
Cheers

[miniZ]

Hi MiniZ,

Your miner is closing with an error, any idea where can I check what kind of error is happening?

I tried to use it on 2 1050 Ti cards and it is always closing after 20-30 mins. I updated the system to a last driver - no success. I used 9.2 and 8 versions - same problem.

Also if I set --intensity 80 (any intensity) the miners stuck like this:



Thank you!

P.S. This is how it stuck:

Hi supervitek,
thanks for reporting this.
Does this problem happen only when using the intensity?
To rule out a possible bug with intensity option we suggest to run miniZ without setting this option. Let us know how did it go.

We also suggest you to use the nocolor option (v1.0i++), for a cleaner console output. v1.0h does not have the nocolor option implemented.
However, you can use another console. We tried ConEmu terminal emulator and it worked fine. There are others available, which should also work OK.

Cheers

[miniZ]

will you be creating a windows cuda 10 version?

Hi alucard20724,
we can add that if it is really necessary. Why would you need a windows cuda 10 version for?
Cheers

[KriptoFull]

will you be creating a windows cuda 10 version?

Hi alucard20724,
we can add that if it is really necessary. Why would you need a windows cuda 10 version for?
Cheers

Hi!Tell me what the parameter shows in the minner  I/s

[miniZ]

will you be creating a windows cuda 10 version?

Hi alucard20724,
we can add that if it is really necessary. Why would you need a windows cuda 10 version for?
Cheers

Hi!Tell me what the parameter shows in the minner  I/s

Hi KriptoFull,

I/s refers to iterations per second. This is roughly half the Sol/s (1 Sol/s = 0.5 I/s), since each equihash iteration/run generates aproximately, on average, 2 solutions. This value can vary but the most probable values range ~0-4 (but can be more). This is why I/s generally stabilizes faster than the Sol/s value, and the latter should always be compared after a few hours.

Cheers

[1ncehost]

Hello, I believe I found a regression that explains why my 1060s were running slower on newest versions.

Two of my cards have poor thermal performance and run hot. I have noticed that on one of my rigs MiniZ runs the hot cards in a different algorithm configuration (the vram usage is higher and the wattage is lower). However, in the other of my rigs, it runs the wrong card in this "hot mode".

If I am correct in understanding how MiniZ works, on this rig my hot card is getting thermally limited by the drivers (and running unoptimally) while simultaniously a cool card is getting limited by MiniZ, running unnecessarily low wattage.

Hope this helps

[thereal35]

Heads up,
I couldnt get this Miner to successfully run my 6x1070 rig.
Turns out that the 16gb Virtual memory i had set on Windows was not enough.
Bumped it up to 18gb (18432) and it was able to start mining.
It actually seemed like it wasnt going to run, and eventually fired up.
I think i need to bump up to at least 20gb virtual mem, but do not have that available on this rig.
Im going to hook up another SSD and set the virtual mem to it instead.

I had the same issue trying to run another miner (BEAM).
even though i have 8gb ram and all 6 GPUs have 8gb, the virtual memory was not enough on my system to run it.
(A 60gb ssd in windows does not hold up over time)

hope this helps someone.