Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 127. (Read 444040 times)
October 18, 2016, 12:00:45 AM
tried cpuminer-xzc, it shows weird (?) 220-230 kh/s hashrate but a pool shows about 60-70 h/s, 48 threads
October 17, 2016, 11:49:48 PM
@joblo,
is it normal to have 11-12 h/s on double e5-2690v3 (2x 12cores x 2threads)? tried different amount of threads, 48,12,24 etc
also cpu usage is only 14-15% in taskmanager
at cryptonight algo it got 750 h/s (48 threads)
is it normal to have 11-12 h/s on double e5-2690v3 (2x 12cores x 2threads)? tried different amount of threads, 48,12,24 etc
also cpu usage is only 14-15% in taskmanager
at cryptonight algo it got 750 h/s (48 threads)
Read back a page or 2, another user had issues with dual xeons.
October 17, 2016, 11:35:16 PM
@joblo,
is it normal to have 11-12 h/s on double e5-2690v3 (2x 12cores x 2threads)? tried different amount of threads, 48,12,24 etc
also cpu usage is only 14-15% in taskmanager
at cryptonight algo it got 750 h/s (48 threads)
is it normal to have 11-12 h/s on double e5-2690v3 (2x 12cores x 2threads)? tried different amount of threads, 48,12,24 etc
also cpu usage is only 14-15% in taskmanager
at cryptonight algo it got 750 h/s (48 threads)
October 17, 2016, 09:21:06 PM
October 17, 2016, 06:17:51 PM
to me are mostly fx 8350 and a few pieces i5 1156 e now in this the miner shows me the h / s eg Fx 8350 accepted 367H, 6,84H / s if this is normal
I can't say what's normal for AMD but your CPU has AES and AVX so you might get better performance using
an Intel build (assuming you're using the binaries) with those features, depending on the algo.
https://bitcointalksearch.org/topic/m.16574607
those where the numbers i got, amd is pretty weak in zcoin algo, though they change it to mpt soon, so that might change
October 17, 2016, 05:41:22 PM
to me are mostly fx 8350 and a few pieces i5 1156 e now in this the miner shows me the h / s eg Fx 8350 accepted 367H, 6,84H / s if this is normal
I can't say what's normal for AMD but your CPU has AES and AVX so you might get better performance using
an Intel build (assuming you're using the binaries) with those features, depending on the algo.
October 17, 2016, 05:23:12 PM
cpuminer 3.4.8 is released.
Source code:
git: https://github.com/JayDDee/cpuminer-opt
tarball: https://drive.google.com/file/d/0B0lVSGQYLJIZMnVmX0Qwcjg1cmc/view?usp=sharing
Windows binaries
https://drive.google.com/file/d/0B0lVSGQYLJIZQkRWSEx1WVNOaWs/view?usp=sharing
It adds support for zcoin lyra2 using either "-a zcoin" or "-a lyra2z". Lyra2RE (lyra2) and lyra2REv2 (lyra2v2)
still work as usual.
Although I have optimixed it for AVX2 there was no observable change in performance in my testing.
I suspect the algo is I/O bound meaning the CPU spends a lot of time waiting on data from memory.
LGA2011 systems with 4 channel DDR may do better. Feedback is appreciated.
The diff display for cryptonight in the API has been fixed.
Changes in diff will now be displayed by default (--show-diff). Use "--hide-diff" to disable.
Removed some cpuminer-multi artifacts.
I am considering dropping the btver1 build from the Windows binaries package. Before I do so I would like to
know if anyone is using it and whether it performs better on an AMD CPU than any of the Intel builds. The
btver1 build does not include any optimizartions so is not suitable for recent AMD CPUs.
Source code:
git: https://github.com/JayDDee/cpuminer-opt
tarball: https://drive.google.com/file/d/0B0lVSGQYLJIZMnVmX0Qwcjg1cmc/view?usp=sharing
Windows binaries
https://drive.google.com/file/d/0B0lVSGQYLJIZQkRWSEx1WVNOaWs/view?usp=sharing
It adds support for zcoin lyra2 using either "-a zcoin" or "-a lyra2z". Lyra2RE (lyra2) and lyra2REv2 (lyra2v2)
still work as usual.
Although I have optimixed it for AVX2 there was no observable change in performance in my testing.
I suspect the algo is I/O bound meaning the CPU spends a lot of time waiting on data from memory.
LGA2011 systems with 4 channel DDR may do better. Feedback is appreciated.
The diff display for cryptonight in the API has been fixed.
Changes in diff will now be displayed by default (--show-diff). Use "--hide-diff" to disable.
Removed some cpuminer-multi artifacts.
I am considering dropping the btver1 build from the Windows binaries package. Before I do so I would like to
know if anyone is using it and whether it performs better on an AMD CPU than any of the Intel builds. The
btver1 build does not include any optimizartions so is not suitable for recent AMD CPUs.
to me are mostly fx 8350 and a few pieces i5 1156 e now in this the miner shows me the h / s eg Fx 8350 accepted 367H, 6,84H / s if this is normal
October 17, 2016, 05:13:53 PM
The source tarball and Windows binares will display incorrect version information. The code is fine.
The version is now fixed in git.
The version is now fixed in git.
cpuminer 3.4.8 is released.
Source code:
git: https://github.com/JayDDee/cpuminer-opt
tarball: https://drive.google.com/file/d/0B0lVSGQYLJIZMnVmX0Qwcjg1cmc/view?usp=sharing
Windows binaries
https://drive.google.com/file/d/0B0lVSGQYLJIZQkRWSEx1WVNOaWs/view?usp=sharing
It adds support for zcoin lyra2 using either "-a zcoin" or "-a lyra2z". Lyra2RE (lyra2) and lyra2REv2 (lyra2v2)
still work as usual.
Although I have optimixed it for AVX2 there was no observable change in performance in my testing.
I suspect the algo is I/O bound meaning the CPU spends a lot of time waiting on data from memory.
LGA2011 systems with 4 channel DDR may do better. Feedback is appreciated.
The diff display for cryptonight in the API has been fixed.
Changes in diff will now be displayed by default (--show-diff). Use "--hide-diff" to disable.
Removed some cpuminer-multi artifacts.
I am considering dropping the btver1 build from the Windows binaries package. Before I do so I would like to
know if anyone is using it and whether it performs better on an AMD CPU than any of the Intel builds. The
btver1 build does not include any optimizartions so is not suitable for recent AMD CPUs.
Source code:
git: https://github.com/JayDDee/cpuminer-opt
tarball: https://drive.google.com/file/d/0B0lVSGQYLJIZMnVmX0Qwcjg1cmc/view?usp=sharing
Windows binaries
https://drive.google.com/file/d/0B0lVSGQYLJIZQkRWSEx1WVNOaWs/view?usp=sharing
It adds support for zcoin lyra2 using either "-a zcoin" or "-a lyra2z". Lyra2RE (lyra2) and lyra2REv2 (lyra2v2)
still work as usual.
Although I have optimixed it for AVX2 there was no observable change in performance in my testing.
I suspect the algo is I/O bound meaning the CPU spends a lot of time waiting on data from memory.
LGA2011 systems with 4 channel DDR may do better. Feedback is appreciated.
The diff display for cryptonight in the API has been fixed.
Changes in diff will now be displayed by default (--show-diff). Use "--hide-diff" to disable.
Removed some cpuminer-multi artifacts.
I am considering dropping the btver1 build from the Windows binaries package. Before I do so I would like to
know if anyone is using it and whether it performs better on an AMD CPU than any of the Intel builds. The
btver1 build does not include any optimizartions so is not suitable for recent AMD CPUs.
October 17, 2016, 05:12:05 PM
cpuminer 3.4.8 is released.
testing, thanks!
version reports 3.4.8-dev, is this intended for releases?
edit: also version on startup in console reports 4.3.8
That was a pretty stupid mistake, two actually.
The tarball and binaries have the right code, but wrong version. Fixed the version in GIT.
October 17, 2016, 04:54:31 PM
cpuminer 3.4.8 is released.
Source code:
git: https://github.com/JayDDee/cpuminer-opt
tarball: https://drive.google.com/file/d/0B0lVSGQYLJIZMnVmX0Qwcjg1cmc/view?usp=sharing
Windows binaries
https://drive.google.com/file/d/0B0lVSGQYLJIZQkRWSEx1WVNOaWs/view?usp=sharing
It adds support for zcoin lyra2 using either "-a zcoin" or "-a lyra2z". Lyra2RE (lyra2) and lyra2REv2 (lyra2v2)
still work as usual.
Although I have optimixed it for AVX2 there was no observable change in performance in my testing.
I suspect the algo is I/O bound meaning the CPU spends a lot of time waiting on data from memory.
LGA2011 systems with 4 channel DDR may do better. Feedback is appreciated.
The diff display for cryptonight in the API has been fixed.
Changes in diff will now be displayed by default (--show-diff). Use "--hide-diff" to disable.
Removed some cpuminer-multi artifacts.
I am considering dropping the btver1 build from the Windows binaries package. Before I do so I would like to
know if anyone is using it and whether it performs better on an AMD CPU than any of the Intel builds. The
btver1 build does not include any optimizartions so is not suitable for recent AMD CPUs.
Source code:
git: https://github.com/JayDDee/cpuminer-opt
tarball: https://drive.google.com/file/d/0B0lVSGQYLJIZMnVmX0Qwcjg1cmc/view?usp=sharing
Windows binaries
https://drive.google.com/file/d/0B0lVSGQYLJIZQkRWSEx1WVNOaWs/view?usp=sharing
It adds support for zcoin lyra2 using either "-a zcoin" or "-a lyra2z". Lyra2RE (lyra2) and lyra2REv2 (lyra2v2)
still work as usual.
Although I have optimixed it for AVX2 there was no observable change in performance in my testing.
I suspect the algo is I/O bound meaning the CPU spends a lot of time waiting on data from memory.
LGA2011 systems with 4 channel DDR may do better. Feedback is appreciated.
The diff display for cryptonight in the API has been fixed.
Changes in diff will now be displayed by default (--show-diff). Use "--hide-diff" to disable.
Removed some cpuminer-multi artifacts.
I am considering dropping the btver1 build from the Windows binaries package. Before I do so I would like to
know if anyone is using it and whether it performs better on an AMD CPU than any of the Intel builds. The
btver1 build does not include any optimizartions so is not suitable for recent AMD CPUs.
testing, thanks!
version reports 4.3.8-dev, is this intended for releases? (also 3 and 4 are swapped it seems)
October 17, 2016, 03:34:14 PM
yep, but remains a weird algo that remember me riecoin stuff
that remember me riecoin stuff 
October 17, 2016, 03:27:26 PM
joblo, you're probably already aware of the Tromp's Equihash solvers, which were released under open-source. Are you considering implementing them into your cpuminer-opt, thus adding support for equihash algortihm (for z.cash)?
That's a cuda miner, still looking for a CPU miner.
Not true. It has fastest to-date known public CPU implementation as well as CUDA implementation.
October 17, 2016, 02:35:55 PM
cpuminer 3.4.8 is released.
Source code:
git: https://github.com/JayDDee/cpuminer-opt
New links to fix version error.
tarball:https://drive.google.com/file/d/0B0lVSGQYLJIZMnVmX0Qwcjg1cmc/view?usp=sharing
https://drive.google.com/file/d/0B0lVSGQYLJIZQndVQkx1ZldSTTg/view?usp=sharing
Windows binaries
https://drive.google.com/file/d/0B0lVSGQYLJIZQkRWSEx1WVNOaWs/view?usp=sharing
https://drive.google.com/file/d/0B0lVSGQYLJIZc2xFWW5mdUZaU1k/view?usp=sharing
It adds support for zcoin lyra2 using either "-a zcoin" or "-a lyra2z". Lyra2RE (lyra2) and lyra2REv2 (lyra2v2)
still work as usual.
Although I have optimixed it for AVX2 there was no observable change in performance in my testing.
I suspect the algo is I/O bound meaning the CPU spends a lot of time waiting on data from memory.
LGA2011 systems with 4 channel DDR may do better. Feedback is appreciated.
The diff display for cryptonight in the API has been fixed.
Changes in diff will now be displayed by default (--show-diff). Use "--hide-diff" to disable.
Removed some cpuminer-multi artifacts.
I am considering dropping the btver1 build from the Windows binaries package. Before I do so I would like to
know if anyone is using it and whether it performs better on an AMD CPU than any of the Intel builds. The
btver1 build does not include any optimizartions so is not suitable for recent AMD CPUs.
Source code:
git: https://github.com/JayDDee/cpuminer-opt
New links to fix version error.
tarball:
https://drive.google.com/file/d/0B0lVSGQYLJIZQndVQkx1ZldSTTg/view?usp=sharing
Windows binaries
https://drive.google.com/file/d/0B0lVSGQYLJIZc2xFWW5mdUZaU1k/view?usp=sharing
It adds support for zcoin lyra2 using either "-a zcoin" or "-a lyra2z". Lyra2RE (lyra2) and lyra2REv2 (lyra2v2)
still work as usual.
Although I have optimixed it for AVX2 there was no observable change in performance in my testing.
I suspect the algo is I/O bound meaning the CPU spends a lot of time waiting on data from memory.
LGA2011 systems with 4 channel DDR may do better. Feedback is appreciated.
The diff display for cryptonight in the API has been fixed.
Changes in diff will now be displayed by default (--show-diff). Use "--hide-diff" to disable.
Removed some cpuminer-multi artifacts.
I am considering dropping the btver1 build from the Windows binaries package. Before I do so I would like to
know if anyone is using it and whether it performs better on an AMD CPU than any of the Intel builds. The
btver1 build does not include any optimizartions so is not suitable for recent AMD CPUs.
October 17, 2016, 12:51:04 PM
joblo, you're probably already aware of the Tromp's Equihash solvers, which were released under open-source. Are you considering implementing them into your cpuminer-opt, thus adding support for equihash algortihm (for z.cash)?
That's a cuda miner, still looking for a CPU miner.
Hello guys Anybody has optimized miner XZC order is free
October 17, 2016, 10:04:30 AM
joblo, you're probably already aware of the Tromp's Equihash solvers, which were released under open-source. Are you considering implementing them into your cpuminer-opt, thus adding support for equihash algortihm (for z.cash)?
That's a cuda miner, still looking for a CPU miner.
October 17, 2016, 09:02:45 AM
joblo, you're probably already aware of the Tromp's Equihash solvers, which were released under open-source. Are you considering implementing them into your cpuminer-opt, thus adding support for equihash algortihm (for z.cash)?
October 15, 2016, 11:06:10 PM
Code:
collect2: error: ld returned 1 exit status
Makefile:869: recipe for target 'cpuminer' failed
make[2]: *** [cpuminer] Error 1
make[2]: Leaving directory '/home/ubuntu/cpuminer-xzc'
Makefile:2349: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/ubuntu/cpuminer-xzc'
Makefile:559: recipe for target 'all' failed
make: *** [all] Error 2
That's not cpuminer-opt you're compiling, and cpuminer-opt doesn't support zcoin yet.
Try the zcoin thread and include more info.
October 15, 2016, 07:59:52 PM
Code:
collect2: error: ld returned 1 exit status
Makefile:869: recipe for target 'cpuminer' failed
make[2]: *** [cpuminer] Error 1
make[2]: Leaving directory '/home/ubuntu/cpuminer-xzc'
Makefile:2349: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/ubuntu/cpuminer-xzc'
Makefile:559: recipe for target 'all' failed
make: *** [all] Error 2
October 15, 2016, 07:42:17 PM
optminers version (with some AVX2 optimizations i suppose) is here: https://github.com/Optiminer/cpuminer-xzc
Quote
Code for AVX2 can be enabled by compiling with "-mavx2": $ CFLAGS="-O2 -mavx2" ./configure && make clean && make
Memory prefetching can be enabled by compiling with "-mavx2": $ CFLAGS="-O2 -DROW_PREFETCH" ./configure && make clean && make
Should I compile with both? if so how exactly? (kind of a noob on nix lol)Memory prefetching can be enabled by compiling with "-mavx2": $ CFLAGS="-O2 -DROW_PREFETCH" ./configure && make clean && make
October 15, 2016, 07:06:19 PM
It's defaulting to 12 threads so that tells me that it does take multiple CPU's
also of note, I've got this running on numerous dual 16-core opteron setups and it takes those like a champ... 900H/s
Each CPU can run 12 threads (6 cores hypertthreaded) so it appears you are only using one CPU. With both CPUs it should default
to 24.
interesting.... am I missing something when I compile i wonder? I figured it would automatically pick up the other CPU?
I have no experience with multi CPU configs. You should check your BIOS and OS to make sure everything is setup correctly and make
sure both CPUs are being used. Check the system monitor or whatever tools you have. It should all be transparent to the miner SW.
Adjusting ACPI options in the BIOS did it - running around 350H/s (better, but still a good deal under what I was hoping for... 400+ at least.
Jump to: