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

I was compiling it to other cpu's to test if the speed increase still the same, will try optimizing after this, i'll get back to you with more numbers in a few

Edit :

so i have 2 cpus

Intel(R) Xeon(R) CPU L3426  @ 1.87GHz - SSE2 - 8MB cache L2 - Non fixed thread count (use as much as logical core) - Thread 8

Minergate CLI : ~60 H/s
Cpuminer 3.5.7 :  ~55-56 H/s

Intel(R) Atom(TM) CPU  C2750  @ 2.40GHz - SSE2 / AES - 4MB cache L2 - Non fixed thread count (use as much as logical core) - Thread 8

Minergate CLI : 67-67.5H/s
Cpuminer 3.5.7 : ~68 H/s

So it seems that on AES/SS2 cpu it match and even go a tad above in speed. But for SS2 CPU only, it's better but not on par yet. One thing to note, when i use a lesser thread count than my logical core, it only hash on as much core as the thread allow so it give me less overall hash.

Thanks.

Wow the're pretty close. You might do better with 4 threads depending on your cache size.
threads = cache size MB / 2 MB. Four threads makes a big difference on my i7-6700K.

Excellent work man, it's finally matching minergate private cpu-miner !

Mad props to you  

cpuminer-opt v3.5.7


Minergate cli 4.04


I can finally get rid of minergate, you made me a happy man, donation coming your way 

cpuminer-opt-3.5.7 is released. See OP, link in sig.

nice work joblo ! Maybe we'll get up par to that private miner from minergate I'll be more than willing to test that out !

After a year of trying I've finally made progress improving cryptonight. I think I can get 5% with
a combination of aligning data on a cache line boundary and aggressive prefetching.

Also a reminder the next release will use a new naming scheme for the Windows binaries. The names
indicates the CPU features required to use them. Intel or AMD, choose the one that best matches your CPU's
features. Or you can use trial and error to find the best one.


Prepare to update your scripts, that's bat for Windows users.

dont know what you mean   , pls advice me   i know  they are only sse3 able  but  what shall i do   the package is cheap

beware with the memory types of these :p a mistake could double the price

if i compile from source on Linux by myself its ok . it happens only sometimes with precompiled binary on windows

need to find some cheap Dual cpu board ,socket 771 , have here two E5462 2.8 ghz 12Mb  laying around   lazy things   so i cant test something with them
just now found this one :Serverboard Supermicro X7DBP-I Dual Socket 771   inkl heatsinks ram and  2x E5405  affordable price    holy shi...  75€

I found this regarding the difference between Sandybridge and Ivybridge. Not much. It doesn't
affect targetted code and I have no idea what opimizations the compiler may do to portable
code. It does only apply to the core series, not Pentium G or Celeron.

CORE-AVX-I    May generate Intel® AVX, SSE4.2, SSE4.1, SSSE3, SSE3, SSE2 and SSE instructions for
Intel® processors, including instructions for 3rd generation Intel® Core™ processors. Optimizes for
3rd generation Intel® Core™ processors and the Intel® Xeon® Processor E3 v2, E5 v2 and E7 v2 families.

AVX    May generate Intel® AVX, SSE4.2, SSE4.1, SSSE3, SSE3, SSE2 and SSE instructions for Intel® processors.
Optimizes for 2nd generation Intel® Core™ i7, i5 and i3 processor families and the Intel® Xeon® Processor
E5 and E3 families.

This doesn't seem right. All Sandybridge core-i should have AVX. What happens when you compile native?
What happens when you run the AVX binary? Is this the i7-2600 you mentioned earlier? I have an i5-2400
and it perfoms with AVX as expected.

have also expirenced with my i7 2nd gen (sandybridge)   but wont work when i chose Sandybridge executables ?
on Windows where given binary aviable are and discribed for  this core family
when im using cpum....i7-sse41.exe it works on some miner´s

Thanks. It looks like Pentium G may be like Westmere, AES without AVX.
The fallback in any case where native compile doesn't match with the CPUs features is to specify
them manually with -m.

pentium G can have problems also, native seems to enable AVX which is not on these... but was maybe fixed in the recent gcc.. was the case with 4.8/4.9

I little correction, the family name doesn't always work. On Intel native should always work. One exception
is Westmeme where the native compile may fail to generate AES code. Any Westmere users who compile
there own could confirm. AMD is more difficult, the brand names sometimes work but don't seem to
generate optimum code. My best advoce for AMD users is to choose the arch that best matches the CPUs features.
AMD users who compile may have better advice.

The Windows binaries are all built as follows, most users can find the right fit.

Core2 is "-march=core2".
Nehalem does not have AES or AVX, the arch name is -march=corei7
There aren't any feature differences between core2 and Nehalem that affect cpouminer.
Westemere does have AES but does not have AVX, there is no compile arch name, use "-maes, -msse4.2"
Sandybridge has AES and AVX, the archname is "-march=corei7-avx"
Ivybridge has AES and AVX but it's own arch name "-march=core-avx-i", not built
There are no feature differences between Sandybridge and Ivybridge that affect cpuminer, I build corei7-avx.
Haswell and above use "-march=core-avx2"

if someone have troubles to compile the right Arch

different CPU architecture:


nocona = Pentium 4 with 64-bit support
core2 = Intel® Core2™ Family
nehalem = 1st Generation Intel® Core™ (also westmere)
sandybridge = 2nd Generation Intel® Core™ (also ivybridge)
haswell = 4th Generation Intel® Core™ (also broadwell & skylake)
bonnell = Early Generation Intel® Atom™
silvermont = Current Generation Intel® Atom™
athlon64 = AMD K8 / Athlon 64 / Athlon 64 FX
barcelona = AMD K10 / Phenom / Phenom 2 / Athlon II
bdver1 = AMD 15h / Bulldozer
bdver2 = AMD 15h / Piledriver
bdver3 = AMD 15h / Steamroller
bdver4 = AMD 15h / Excavator
btver1 = AMD 14h / Bobcat
btver2 = AMD 16h / Jaguar

Example :CFLAGS="-O3 -march=barcelona -Wall" CXXFLAGS="$CFLAGS -std=gnu++11" ./configure --with-curl


the red one has to be changed to match your cpu architecture , if failed with "march=native"

yes you are right joblo , thats the old crap  athlon 64x2 5600+

That's not what an i7-2600 looks like, it's more like some ancient AMD without any advanced features
or a proper CPU ID.

their wallet is not ready to serve yiimp, not enough multi tasks, there are often rpc locks for minutes even on the command line to do a getinfo

yesterday 21h ago tested for short lyra2z on Yiimp

3.5.6 , ubuntu 16.04LTS , i7 2600 ,  8 cores =261kh/s  TTF 3 years   lol

other stuff wont working   im giving up , tried all possible variants and releases 3.3.8 , 3.4.12 , 3.5.6  no succes  allways same error   shit happens  then no    stupid donkey Amd

never say " give up "

 
         **********  cpuminer-opt 3.5.6  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU: <---------------------------------------------------  good performance without CPU  Athlon 64 x2 5600+
CPU features: SSE2
SW built on Feb 13 2017 with GCC 5.4.0
SW features: SSE2
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2

[2017-02-13 22:06:21] Starting Stratum on stratum+tcp://yiimp.ccminer.org:3555
[2017-02-13 22:06:21] 2 miner threads started, using 'timetravel' algorithm.
[2017-02-13 22:06:21] Stratum difficulty set to 0.125 (0.00049)
[2017-02-13 22:06:21] timetravel block 394362, diff 3.121
[2017-02-13 22:06:24] CPU #0: 65.54 kH, 40.60 kH/s
[2017-02-13 22:06:24] CPU #1: 65.54 kH, 40.87 kH/s
[2017-02-13 22:06:24] CPU #1: 11.53 kH, 42.10 kH/s
[2017-02-13 22:06:24] Accepted 1/1 (100%), 77.06 kH, 82.70 kH/s, 0C
[2017-02-13 22:06:53] CPU #1: 1253.17 kH, 42.39 kH/s
[2017-02-13 22:06:54] Accepted 2/2 (100%), 1318.71 kH, 82.99 kH/s, 0C
[2017-02-13 22:06:56] CPU #1: 121.96 kH, 42.35 kH/s
[2017-02-13 22:06:56] CPU #0: 1380.04 kH, 42.17 kH/s
[2017-02-13 22:07:04] CPU #1: 302.09 kH, 42.39 kH/s
[2017-02-13 22:07:04] Accepted 3/3 (100%), 1682.13 kH, 84.57 kH/s, 0C
[2017-02-13 22:07:57] CPU #0: 2530.32 kH, 41.45 kH/s
[2017-02-13 22:08:00] CPU #0: 86.71 kH, 41.47 kH/s
[2017-02-13 22:08:00] CPU #1: 2323.64 kH, 41.49 kH/s
[2017-02-13 22:08:02] CPU #0: 89.60 kH, 41.09 kH/s
[2017-02-13 22:08:02] Accepted 4/4 (100%), 2413.24 kH, 82.58 kH/s, 0C
[2017-02-13 22:08:50] CPU #1: 2138.19 kH, 42.35 kH/s
[2017-02-13 22:08:50] Accepted 5/5 (100%), 2227.79 kH, 83.44 kH/s, 0C
[2017-02-13 22:09:00] CPU #0: 2465.52 kH, 42.23 kH/s
[2017-02-13 22:09:03] CPU #0: 107.11 kH, 41.65 kH/s
[2017-02-13 22:09:03] CPU #1: 535.73 kH, 42.34 kH/s
[2017-02-13 22:09:20] CPU #0: 722.92 kH, 42.24 kH/s
[2017-02-13 22:09:20] Accepted 6/6 (100%), 1258.65 kH, 84.58 kH/s, 0C
[2017-02-13 22:09:22] CPU #1: 827.50 kH, 42.37 kH/s
[2017-02-13 22:09:22] Accepted 7/7 (100%), 1550.42 kH, 84.61 kH/s, 0C
[2017-02-13 22:09:45] CPU #1: 951.98 kH, 42.38 kH/s
[2017-02-13 22:09:45] Accepted 8/8 (100%), 1674.89 kH, 84.63 kH/s, 0C
[2017-02-13 22:09:54] CPU #1: 394.54 kH, 42.37 kH/s
[2017-02-13 22:09:54] Accepted 9/9 (100%), 1117.45 kH, 84.61 kH/s, 0C  <-------  +10kh/s compared to before with other miner

as well Athlon II x2 250  doing too great job , dont wanna tell number´s   only that he beat some i3 , i5   and that with only 2 cores

so we have now fresh " Orange-Juice"   cheers   thank´a lot to you Guy´s