Pages:
Author

Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 40. (Read 444067 times)

newbie
Activity: 18
Merit: 5
Greetings, I am a user of Ubuntu 17.10 and my CPU is an i3 2100, after the last updates I could not use the program, chose to throw me the following error:

./cpuminer -a x11 --benchmark

         **********  cpuminer-opt 3.7.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX2 and SHA extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT

CPU:         Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz.
SW built on Jan  4 2018 with GCC 6.4.0.
CPU features: SSE2 AVX.
SW features: SSE2 AVX.
Algo features: SSE2 AES AVX2 4WAY.
A CPU with AES and AVX2 is required!

I compile it using flag -march=native.

The only way to use it is to compile it from build-allarch.sh and using the executable cpuminer-sse42. Thanks in advance for any assistance.
newbie
Activity: 3
Merit: 0
I am on miningpoolhub and it's decent.
newbie
Activity: 7
Merit: 0
Is there any solution? Is it more effective to mine on another pool?
legendary
Activity: 1470
Merit: 1114
Nicehash sets the difficulty too high for cryptonight. It takes too long to find a share so the stratum
times out.
newbie
Activity: 7
Merit: 0
I tried to run on ubuntu but each thread shows 10 hash/s and no block is detected

https://i.imgur.com/plrdHgG.png

It just runs and nothing happens... Sad

Using nicehash EU server however the windows client works at the moment perfect.

Does anyone have a standard example config for nicehash cryptonight for a Ryzen 1700X CPU?


UPDATE:
This is Cryptonight and it does not work at all.
With other algos it works...

Made a debug test and found following:

[2018-01-04 22:13:34] stratum_recv_line failed
[2018-01-04 22:13:34] Stratum connection interrupted


How can I solve this issue?
legendary
Activity: 1470
Merit: 1114
Hi Joblo! 3.7.8 avx-sha is better than ever!

Im mining m7m algo, but I mine with both GPUs and Ryzen. The 16thread mining are slowing down the GPUs mining.

How could I set CPU affinity for all threads but CPU0 (or threads 0 and 1)?

I searched for an option to do it, but I havent found nothing  Undecided

-t 14 --cpu-affinity 0xfffd should mine on logical cores 2 through 15 leaving cores 0 & 1 free.
But I'm not sure threads 0 & 1 are mapped to the same physical core. You might have to
play with the affinity mask to isolate 2 threads on the same physical core.
Other possibilities include 0xfefe (threads 0 & Cool and 0xffee (threads 0 & 4). I can't think of
any other way they could be mapped. Please let us know which one works.
jr. member
Activity: 196
Merit: 1
Hi Joblo! 3.7.8 avx-sha is better than ever!

Im mining m7m algo, but I mine with both GPUs and Ryzen. The 16thread mining are slowing down the GPUs mining.

How could I set CPU affinity for all threads but CPU0 (or threads 0 and 1)?

I searched for an option to do it, but I havent found nothing  Undecided


EDIT:'

I found it:
https://phempshall.github.io/cpuminer-affinity-setter/

works Cheesy
newbie
Activity: 3
Merit: 0
I guess you missed the requirements section in the OP which states a 64 bit CPU & OS are required.

Quote
Requirements:

1. A x86_64 architecture CPU with a minimum of SSE2 support. This includes Intel
Core2 and newer and AMD equivalents. In order to take advantage of AES_NI
optimizations a CPU with AES_NI is required. This includes Intel Westbridge
and newer and AMD equivalents. Further optimizations are available on some algos
for CPUs with AVX and AVX2, Sandybridge and Haswell respectively.

Older CPUs are supported by cpuminer-multi by TPruvot but at reduced performance.

2. 64 bit Linux OS. Ubuntu and Fedora based distributions, including Mint and Centos are known
to work and have all dependencies in their repositories. Others may work but may require
more effort.

64 bit Windows OS is supported using the pre-compiled binaries package or may be compiled
with mingw_w64 and msys.

Where does it say that we can't produce 32bit executable for 64bits cpu's ?
I got core2 cpu's with windows 7 32 bits installed.

It does not explain why it does not want to compile despite giving the good directories (imho) to include, though Smiley .

I did not even tried yet to compile 32bit executables but just wanted to succeed to compile windows executable through mingw32 with the windows-cross.sh provided.

Regards,
legendary
Activity: 1470
Merit: 1114
Hi there !

It's my first message as registered user, but I follow this project for months now Smiley.

I tried to (cross-)compile this project for windows 7 32bits version with no success.


I guess you missed the requirements section in the OP which states a 64 bit CPU & OS are required.
newbie
Activity: 3
Merit: 0
Hi there !

It's my first message as registered user, but I follow this project for months now Smiley.

I tried to (cross-)compile this project for windows 7 32bits version with no success.

I am a vet' sysadmin but not a good programmer at all :p. I installed some VMs with Linux ubuntu LTS 16.04.3 and mingw32 : no success.
I tried to install "native" mingw32 environment on my win7 64 with no success ...
I installed everything needed, I get a good curl install, I get a good openssl install, everything seems right but I get strange messages (yet perfectly understandable but I don't know what to do with mingw32 and msys from there) :

Code:
gcc -DHAVE_CONFIG_H -I. -I/home/XXXX/usr/lib/curl/include -I/home/XXXX/usr/lib/openssl/include (...)
cpu-miner.c:40:25: fatal error : openssl/sha.h : No such file or directory
 #include
                          ^

So, clearly, my directory for include sucks. But what am I doing wrong ? Curl and Openssl are installed and working. I did correctly set up the PATH environment variables in windows (adding every possible /bin from mingw32 and msys). I don't have any /usr/lib directory. The sha.h is in ./include/openssl/sha.h (means c:\mingw\include\openssl\) while curl is in ./include/curl/curl.h.

Where do I specify the good directory ? I tried to mess with the configure and configure.ac file with no success.

Thank you very much for your work and your passion Smiley !

(obviously, if someone could make 32bit march=core2 version out of these sources, it would be awesome Cheesy ).

Regards,
legendary
Activity: 1470
Merit: 1114
looks like there is a regression in 3.7.8:
4way lyra2z started throwing low difficulty shares error

Lyra2z 4way is a mess, that's why the warning is displayed on startup.

First it is not expected to be fast, only a small portion of the algo (blake256) can be paralleled.
The overhead of converting from 4way for blake256 to serial for lyra2 may be greater than the
gain of blake256 4way. I'm using lyra2z as a test bed for blake256. 4way for the lyra2 code is not
being seriously considered because it's already using AVX2.

Blake256 has problems. Only 2 of the 4 lanes produce valid hash, the other 2 always invalid.
In effect it is only working as 2way, when it works at all.

I made a change in 3.7.8 but was unable to test it at the time. It seems it made things worse.
I'm still working on it but there is no guarantee it will be fixed soon.

Thanks for testing.
member
Activity: 473
Merit: 18
looks like there is a regression in 3.7.8:
4way lyra2z started throwing low difficulty shares error

aes-avx2 works fine, and 3.7.7 4way worked fine


Code:
[2018-01-04 15:17:07] 4 miner threads started, using 'lyra2z' algorithm.
[2018-01-04 15:17:07] Starting Stratum on stratum+tcp://europe.lyra2z-hub.miningpoolhub.com:17025
[2018-01-04 15:17:08] Stratum difficulty set to 5
found 2
[2018-01-04 15:33:44] 4 WAY hash nonces submitted: 1
[2018-01-04 15:33:44] Rejected 1/1 (100.0%), 17.73 MH, 370.84 kH/s
[2018-01-04 15:33:44] reject reason: low difficulty share of 6.130744886502982e-8
[2018-01-04 15:33:44] factor reduced to : 0.67
hero member
Activity: 677
Merit: 500
That's very confusing. The output you posted for yescrypt is from the 4way build (avx2 but no sha). There is no
4way in the avx-sha build. I double checked the names just to make sure. They don't match those in README.txt
but that's only the the inclusion of aes in the name. The important features are correct.

The output I posted for yescrypt is from the avx-sha executable, not the avx2 executable.  That's why I'm confused as well.

That's really weird, I'm getting the same thing. I also getting lower hashrate with the 4way build. They were all built using
the winbuild-cross.sh script that clearly shows the compile options and asociated file names.

It looks like trial and error until I sort this out.

More data points, now that m7m is back on ahashpool:

cpuminer-4way-sha.exe getting around 590 kH/s
cpuminer-avx-sha.exe getting around 565 kH/s
cpuminer-aes-avx.exe getting around 575 kH/s
cpuminer-aes-avx2.exe getting around 567 kH/s
cpuminer-4way.exe getting around 543 kH/s
cpuminer-sse2.exe getting around 550 kH/s
cpuminer-sse42.exe getting around 540 kH/s
cpuminer-aes-sse42.exe getting around 540 kH/s

I found the problem. The avx-sha build is just a copy of the avx2 build. There was a "make clean" missing
in the script so it didn't recompile for avx-sha and just reused the previous build. Your test results make more sense now.

I'm rebuilding now and will upload a windows v2 build.

Thanks for finding this.

Regarding the planned name changes, I'm waiting because I intend to remove 4way as a seperate build if
it's stable. The AVX2 builds will automatically have 4way enabled which will help reduce the number of
targets I have to build. I'll finalize the naming afterward.

Thanks, mate.  Have a happy new year.
legendary
Activity: 1470
Merit: 1114
That's very confusing. The output you posted for yescrypt is from the 4way build (avx2 but no sha). There is no
4way in the avx-sha build. I double checked the names just to make sure. They don't match those in README.txt
but that's only the the inclusion of aes in the name. The important features are correct.

The output I posted for yescrypt is from the avx-sha executable, not the avx2 executable.  That's why I'm confused as well.

That's really weird, I'm getting the same thing. I also getting lower hashrate with the 4way build. They were all built using
the winbuild-cross.sh script that clearly shows the compile options and asociated file names.

It looks like trial and error until I sort this out.

More data points, now that m7m is back on ahashpool:

cpuminer-4way-sha.exe getting around 590 kH/s
cpuminer-avx-sha.exe getting around 565 kH/s
cpuminer-aes-avx.exe getting around 575 kH/s
cpuminer-aes-avx2.exe getting around 567 kH/s
cpuminer-4way.exe getting around 543 kH/s
cpuminer-sse2.exe getting around 550 kH/s
cpuminer-sse42.exe getting around 540 kH/s
cpuminer-aes-sse42.exe getting around 540 kH/s

I found the problem. The avx-sha build is just a copy of the avx2 build. There was a "make clean" missing
in the script so it didn't recompile for avx-sha and just reused the previous build. Your test results make more sense now.

I'm rebuilding now and will upload a windows v2 build.

Thanks for finding this.

Regarding the planned name changes, I'm waiting because I intend to remove 4way as a seperate build if
it's stable. The AVX2 builds will automatically have 4way enabled which will help reduce the number of
targets I have to build. I'll finalize the naming afterward.
hero member
Activity: 677
Merit: 500
That's very confusing. The output you posted for yescrypt is from the 4way build (avx2 but no sha). There is no
4way in the avx-sha build. I double checked the names just to make sure. They don't match those in README.txt
but that's only the the inclusion of aes in the name. The important features are correct.

The output I posted for yescrypt is from the avx-sha executable, not the avx2 executable.  That's why I'm confused as well.

That's really weird, I'm getting the same thing. I also getting lower hashrate with the 4way build. They were all built using
the winbuild-cross.sh script that clearly shows the compile options and asociated file names.

It looks like trial and error until I sort this out.

More data points, now that m7m is back on ahashpool:

cpuminer-4way-sha.exe getting around 590 kH/s
cpuminer-avx-sha.exe getting around 565 kH/s
cpuminer-aes-avx.exe getting around 575 kH/s
cpuminer-aes-avx2.exe getting around 567 kH/s
cpuminer-4way.exe getting around 543 kH/s
cpuminer-sse2.exe getting around 550 kH/s
cpuminer-sse42.exe getting around 540 kH/s
cpuminer-aes-sse42.exe getting around 540 kH/s


legendary
Activity: 1470
Merit: 1114
That's very confusing. The output you posted for yescrypt is from the 4way build (avx2 but no sha). There is no
4way in the avx-sha build. I double checked the names just to make sure. They don't match those in README.txt
but that's only the the inclusion of aes in the name. The important features are correct.

The output I posted for yescrypt is from the avx-sha executable, not the avx2 executable.  That's why I'm confused as well.

That's really weird, I'm getting the same thing. I also getting lower hashrate with the 4way build. They were all built using
the winbuild-cross.sh script that clearly shows the compile options and asociated file names.

It looks like trial and error until I sort this out.
hero member
Activity: 677
Merit: 500
That's very confusing. The output you posted for yescrypt is from the 4way build (avx2 but no sha). There is no
4way in the avx-sha build. I double checked the names just to make sure. They don't match those in README.txt
but that's only the the inclusion of aes in the name. The important features are correct.

The output I posted for yescrypt is from the avx-sha executable, not the avx2 executable.  That's why I'm confused as well.
legendary
Activity: 1470
Merit: 1114
cpuminer-opt-3.7.8 add partial 4way optimizations to most X algos including c11, x11gost,
xevan, phi1612, hsr.

https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.7.8

Awesome!  And I see official SHA support!  Should also add that to the "what's new". Smiley

I'm going to test avx-sha vs 4-way-sha on my Ryzen to see which is more quicker.  And just for kicks, will compare to just straight avx.

Thanks, and hope you have a happy new year!

Update:
Either it's reporting incorrectly, or there's other optimizations going on.

Mining yescrypt:

Code:

         **********  cpuminer-opt 3.7.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX2 and SHA extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT

CPU: AMD Ryzen Threadripper 1950X 16-Core Processor .
SW built on Dec 30 2017 with GCC 5.3.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 4WAY.
Algo features: SSE2 SHA.
Start mining with SSE2.

This is using avx-sha.exe - it doesn't list SHA in SW features.  However, there is definitely an improvement in performance, though not really with yescrypt.  Went from the previous avx-only EXE of 15.22 kH/s to now 15.32 kH/s, but within margin of error.

However, xevan went from a 409.3 kH/s to 453.6 kK/s!!!

What's interesting is that it lists 4WAY as a feature, which I thought wasn't a part of the avx-sha.exe build.

Just to see if the avx-sha.exe build was any different than just avx only, I tried the closes avx-only build. With aes-avx.exe, I get about 14.9 kH/s for yescrypt and 413.8 kH/s for xevan.

So definitely an improvement, but not on the algo I expected.

Update 2:
Also noticed some mismatched builds from Readme.txt.

Actual builds:
Code:
cpuminer-4way-sha.exe
cpuminer-4way.exe
cpuminer-aes-avx.exe
cpuminer-aes-avx2.exe
cpuminer-aes-sse42.exe
cpuminer-avx-sha.exe
cpuminer-sse2.exe
cpuminer-sse42.exe

From readme.txt"
Code:
Exe name                Compile flags              Arch name

cpuminer-sse2.exe      "-march=core2"              Core2  
cpuminer-sse42.exe     "-march=corei7"             Nehalem
cpuminer-aes-sse42.exe "-maes -msse4.2"            Westmere
cpuminer-avx.exe       "-march=corei7-avx"         Sandybridge, Ivybridge
cpuminer-avx2.exe      "-march=core-avx2"          Haswell...
cpuminer-avx-sha       "-march=corei7-avx -msha"   Ryzen...
cpuminer-4way.exe      "-march=core-avx2 -DFOUR_WAY"       same as avx2
cpuminer-4way-sha.exe  "-march=core-avx2 -msha -DFOUR_WAY" same as avx2-sha

Perhaps the names just needs to be matched up.


That's very confusing. The output you posted for yescrypt is from the 4way build (avx2 but no sha). There is no
4way in the avx-sha build. I double checked the names just to make sure. They don't match those in README.txt
but that's only the the inclusion of aes in the name. The important features are correct.
hero member
Activity: 677
Merit: 500
cpuminer-opt-3.7.8 add partial 4way optimizations to most X algos including c11, x11gost,
xevan, phi1612, hsr.

https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.7.8

Awesome!  And I see official SHA support!  Should also add that to the "what's new". Smiley

I'm going to test avx-sha vs 4-way-sha on my Ryzen to see which is more quicker.  And just for kicks, will compare to just straight avx.

Thanks, and hope you have a happy new year!

Update:
Either it's reporting incorrectly, or there's other optimizations going on.

Mining yescrypt:

Code:

         **********  cpuminer-opt 3.7.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX2 and SHA extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT

CPU: AMD Ryzen Threadripper 1950X 16-Core Processor .
SW built on Dec 30 2017 with GCC 5.3.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 4WAY.
Algo features: SSE2 SHA.
Start mining with SSE2.

This is using avx-sha.exe - it doesn't list SHA in SW features.  However, there is definitely an improvement in performance, though not really with yescrypt.  Went from the previous avx-only EXE of 15.22 kH/s to now 15.32 kH/s, but within margin of error.

However, xevan went from a 409.3 kH/s to 453.6 kK/s!!!

What's interesting is that it lists 4WAY as a feature, which I thought wasn't a part of the avx-sha.exe build.

Just to see if the avx-sha.exe build was any different than just avx only, I tried the closes avx-only build. With aes-avx.exe, I get about 14.9 kH/s for yescrypt and 413.8 kH/s for xevan.

So definitely an improvement, but not on the algo I expected.

Update 2:
Also noticed some mismatched builds from Readme.txt.

Actual builds:
Code:
cpuminer-4way-sha.exe
cpuminer-4way.exe
cpuminer-aes-avx.exe
cpuminer-aes-avx2.exe
cpuminer-aes-sse42.exe
cpuminer-avx-sha.exe
cpuminer-sse2.exe
cpuminer-sse42.exe

From readme.txt"
Code:
Exe name                Compile flags              Arch name

cpuminer-sse2.exe      "-march=core2"              Core2  
cpuminer-sse42.exe     "-march=corei7"             Nehalem
cpuminer-aes-sse42.exe "-maes -msse4.2"            Westmere
cpuminer-avx.exe       "-march=corei7-avx"         Sandybridge, Ivybridge
cpuminer-avx2.exe      "-march=core-avx2"          Haswell...
cpuminer-avx-sha       "-march=corei7-avx -msha"   Ryzen...
cpuminer-4way.exe      "-march=core-avx2 -DFOUR_WAY"       same as avx2
cpuminer-4way-sha.exe  "-march=core-avx2 -msha -DFOUR_WAY" same as avx2-sha

Perhaps the names just needs to be matched up.
legendary
Activity: 1470
Merit: 1114
cpuminer-opt-3.7.8 add partial 4way optimizations to most X algos including c11, x11gost,
xevan, phi1612, hsr.

https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.7.8
Pages:
Jump to: