Miner- [NiceHash] Zcash CPU/GPU for Linux and Windows

980ti does 25 Sols/s

1 Like

Thanks for your work. Will your GPU miner support stratum connection ?

I test EU server today and all work…

According to the source code it use the AVX2, but I do not know if it is good price/performance…

If there are any problems with connection to the servers it is (probably) due to the instability of the pools (those that are currently used on orders of the buyers).

8.5 Sol/s = ~ 4 - 4.5 H/s :wink:

this is great :slight_smile: so we ar waithing for your big release :slight_smile:

@nicehashdev
I am getting following error while building nheqminer.

g++ -c -m64 -pipe -std=gnu++11 -O3 -Wall -W -fPIC -DHAVE_DECL_HTOBE16 -DHAVE_DECL_HTOLE16 -DHAVE_DECL_BE16TOH -DHAVE_DECL_LE16TOH -DHAVE_DECL_HTOBE32 -DHAVE_DECL_HTOLE32 -DHAVE_DECL_BE32TOH -DHAVE_DECL_LE32TOH -DHAVE_DECL_HTOBE64 -DHAVE_DECL_HTOLE64 -DHAVE_DECL_BE64TOH -DHAVE_DECL_LE64TOH -DHAVE_BYTESWAP_H -DHAVE_DECL_BSWAP_16 -DHAVE_DECL_BSWAP_32 -DHAVE_DECL_BSWAP_64 -I…/nheqminer -I. -I…/nheqminer/3rdparty -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g+±64 -o main.o …/nheqminer/main.cpp
In file included from …/nheqminer/3rdparty/boost/predef/hardware/simd.h:9:0,
from …/nheqminer/3rdparty/boost/predef/hardware.h:14,
from …/nheqminer/3rdparty/boost/predef.h:20,
from …/nheqminer/3rdparty/boost/smart_ptr/detail/yield_k.hpp:28,
from …/nheqminer/3rdparty/boost/smart_ptr/detail/spinlock_sync.hpp:18,
from …/nheqminer/3rdparty/boost/smart_ptr/detail/spinlock.hpp:50,
from …/nheqminer/3rdparty/boost/smart_ptr/detail/spinlock_pool.hpp:25,
from …/nheqminer/3rdparty/boost/smart_ptr/shared_ptr.hpp:35,
from …/nheqminer/3rdparty/boost/shared_ptr.hpp:17,
from …/nheqminer/3rdparty/boost/signals2/deconstruct.hpp:28,
from …/nheqminer/3rdparty/boost/signals2.hpp:15,
from …/nheqminer/libstratum/ZcashStratum.h:10,
from …/nheqminer/libstratum/StratumClient.h:6,
from …/nheqminer/main.cpp:8:
…/nheqminer/3rdparty/boost/predef/hardware/simd/x86.h:13:53: fatal error: boost/predef/hardware/simd/x86/versions.h: No such file or directory
compilation terminated.
Makefile:1859: recipe for target ‘main.o’ failed

Better use cmake.

Is it possible to run this miner pointing to zmine.io?
I have built it from GitHub - ocminer/nheqminer: Equihash miner for NiceHash and used this command:

./nheqminer -l stratum+tcp://zmine.io:1337 -u tmScaQLdi6qrdYU8GNtqbTTpfh7PbyH2Noh

It keeps then saying:

[14:22:19][0x00007f408f772700] stratum | Connecting to stratum server stratum+tcp://zmine.io:1337
[14:22:19][0x00007f408f772700] stratum | resolve: Service not found
[14:22:19][0x00007f408f772700] stratum | Reconnecting in 3 seconds…

Zmine.io seems to be running and mining so I assume the problem to be on my end.

1 Like

Omit the stratum+tcp:// part from the argument - supply just the hostname and port.

2 Likes

No. H/s and Sol/s are the same.

Edit: Apparently not this time. We really need this to be standardized :smiling_imp:

Not this miner. Your H/S is always double your Sol/s rate. You are given two results each run.

H/s and Sol/s can be the same. Namely if the H refers to the hash applied to solutions. But some people are using H to denote a single run of Equihash (which is not a hash function). So for them H/s is quite different from Sol/s.

If you want to check whether people know what they’re talking about when saying H/s, ask them what hash function H stands for. If they say Equihash, then educate them by explaining that it’s not a hash function. If they say SHA256d, then ask them if they mean the single SHA256d that’s applied to Equihash solutions to check if they meet the difficulty target. If they say yes, then ask them “Why not use the simple Sol/s instead?”

CONCLUSION:

Use only Sol/s to be perfectly clear. Avoid using H/s because it’s ambiguous.

6 Likes

No, each run gives from 0 to 8 solutions.
If you try millions of runs, you might run into a few 9 or more solutions,
but otherwise don’t expect to see those.
The average is not 2 either, and depends both on the (n,k) parameters
and on the solving algorithm.

1 Like

Hi Tromp, great discussion. So do i follow H or Sols here?

[09:47:48][0x00007fe6b4d6e740] Speed [300 sec]: 13.7067 H/s, 26.0767 Sol/s
[09:47:49][0x00007fe6aa7fc700] stratum | Submitting share #971, nonce 07000000000000000000000000000000000000000000000000000027
[09:47:49][0x00007fe6b3230700] stratum | Accepted share #971

That H appears to denote equiHash runs.
Perhaps it would be better of them to report

26.0767 Sol/s, 1.9025 Sol/run

1 Like

thanks Tromp, now it makes better sense.

We will most likely rename H/s into something like I/s (iterations per second). On website, we still have H/s due to the reason that every other algorithm has H and since we have large operation going on, changing this H to Sols is not so trivial.

Anyway, our latest miner is two times faster than last one. CPU i7 5930K does following:

        ==================== www.nicehash.com ====================
            Equihash CPU&GPU Miner for NiceHash v0.2a
    Thanks to Zcash developers for providing base of the code.
        Special thanks to tromp and xenoncat for providing
             optimized CPU and CUDA equihash solvers.
    ==================== www.nicehash.com ====================

Setting log level to 2
[2016-10-25 19:43:03.461687][0x00001c74]: Using SSE2: YES
[2016-10-25 19:43:03.464621][0x00001c74]: Using AVX: YES
[2016-10-25 19:43:03.466576][0x00001c74]: Using AVX2: YES
[2016-10-25 19:43:03.469502][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.471464][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.475371][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.478302][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.481233][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.485181][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.487138][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.490049][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.493975][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.495933][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.498866][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.501777][0x00001c74]: Benchmarking CPU worker (CPU-XENONCAT-AVX2)
[2016-10-25 19:43:03.504729][0x00001c74]: Benchmark starting... this may take several minutes, please wait...
[2016-10-25 19:43:13.681331][0x00001c74]: Benchmark done!
[2016-10-25 19:43:13.683286][0x00001c74]: Total time : 9945 ms
[2016-10-25 19:43:13.685255][0x00001c74]: Total hashes: 200
[2016-10-25 19:43:13.687210][0x00001c74]: Total solutions found: 412
[2016-10-25 19:43:13.689164][0x00001c74]: Speed: 20.1106 H/s
[2016-10-25 19:43:13.692096][0x00001c74]: Speed: 41.4279 Sols/s
5 Likes

Good Work! and AMD GPU ?

2 Likes