[LOCKED] cpuminer-opt v3.12.3, open source optimized multi-algo CPU miner

[joblo]

cpuminer-opt maximum support only 64 threads CPU? My CPU threads more than 64, how to use it to be able to fully play

There is nothing in cpuminer-opt to limit threads, maybe resource limitations or a system issue.

stumbled upon this:
"__int128 to support more than 64 CPUs"
https://github.com/holyangel/cpuminer-multi/commit/79785056, even with less than 64 tfe3a54b148f12ca736483777686f4bc3

Good stumble, didn't think of the affinity mask overflowing.

Edit: It looks like this breaks affinity other than default, I don't think 128 bit input works from the cli.
Every affinity I entered turned into -1 even with < 64 threads

[1715107539]

1715107539

[1715107539]

1715107539

[1715107539]

1715107539

[1715107539]

1715107539

[1715107539]

1715107539

[sir4o]

No spam please. Don't force me to start a moderated thread.

I really doubt such individuals would consider even a warning, just ban him if you can

[joblo]

No spam please. Don't force me to start a moderated thread.

I really doubt such individuals would consider even a warning, just ban him if you can

I'm often a cynic but the poster removed the post at my request. Thank you.

Edit: what I would have accepted (and still will) is a useful comment or suggestion
with a link for his coin and pool included in his sig. He deserves some credit for being
cooperative.

[lncm]

Hi,
i have downloaded from github. compiled it. and get this:

         **********  cpuminer-opt 3.7.5  ***********
     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) Xeon(R) CPU E5-2623 v4 @ 2.60GHz.
SW built on Dec 11 2017 with GCC 5.4.0.
CPU features: SSE2 AES AVX AVX2.
SW features: SSE2 AES AVX AVX2 4WAY.
Algo features:.
Start mining with no optimizations.

why does it start without Algo features?

i run it with: ./cpuminer -a scrypt:1048576


thanks in advance.

best regards,
freeapp

I noticed it also with windows binary and same script. Is this normal?

[Drag0g0]

Is it possible add many pools like if i want mine pool 1 but its go down so miner go mine pool number 2?

And return pool1 when up again.

[Dastashka]

is it suite for Monero with i7-6700K?

[joblo]

Hi,
i have downloaded from github. compiled it. and get this:

         **********  cpuminer-opt 3.7.5  ***********
     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) Xeon(R) CPU E5-2623 v4 @ 2.60GHz.
SW built on Dec 11 2017 with GCC 5.4.0.
CPU features: SSE2 AES AVX AVX2.
SW features: SSE2 AES AVX AVX2 4WAY.
Algo features:.
Start mining with no optimizations.

why does it start without Algo features?

i run it with: ./cpuminer -a scrypt:1048576


thanks in advance.

best regards,
freeapp

I noticed it also with windows binary and same script. Is this normal?

Yes it's normal and dependent on the algo. It means cpuminer-opt has no optimizations for scrypt algo.

[joblo]

Is it possible add many pools like if i want mine pool 1 but its go down so miner go mine pool number 2?

And return pool1 when up again.

Take a look at the retry options in the help. You can use these in a shell script (bat file) to start a backup pool
if the primary fails. There are a few threads in this forum that discuss ways to do this. There also a few GUI
miner manager porgrams that can do that and more.

[joblo]

is it suite for Monero with i7-6700K?

Use -a cryptonight to mine Monero.

[lncm]

Hi,
i have downloaded from github. compiled it. and get this:

         **********  cpuminer-opt 3.7.5  ***********
     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) Xeon(R) CPU E5-2623 v4 @ 2.60GHz.
SW built on Dec 11 2017 with GCC 5.4.0.
CPU features: SSE2 AES AVX AVX2.
SW features: SSE2 AES AVX AVX2 4WAY.
Algo features:.
Start mining with no optimizations.

why does it start without Algo features?

i run it with: ./cpuminer -a scrypt:1048576


thanks in advance.

best regards,
freeapp

I noticed it also with windows binary and same script. Is this normal?

Yes it's normal and dependent on the algo. It means cpuminer-opt has no optimizations for scrypt algo.

Oh, OK, it's just it previously stated SSE2.

On another subject, I tried 3.7.5 windows binary in my desktop (Ryzen 1700) and all executables fail to start - it states:
"thread xx (random): Scrypt buffer allocation failed Fail: thread xx failed to initiate.

[joblo]

Yes it's normal and dependent on the algo. It means cpuminer-opt has no optimizations for scrypt algo.

Oh, OK, it's just it previously stated SSE2.

On another subject, I tried 3.7.5 windows binary in my desktop (Ryzen 1700) and all executables fail to start - it states:
"thread xx (random): Scrypt buffer allocation failed Fail: thread xx failed to initiate.

I noted the change in feature reporting in the release announcement.

You're out of memory.  You only have enough memory for xx -1 threads.

[joblo]

cpuminer-opt-3.7.6 is released.

Added lyra2h algo for Hppcoin.
Added support for more than 64 CPUs.
Optimized shavite with AES, improves x11 etc.

Get it on git:  https://github.com/JayDDee/cpuminer-opt/releases

More detailed release notes:

Lyra2h has not been tested. It is virtually a clone of lyra2z so it should work.
Please report any problems.

Support for over 64 CPU is limited in that specifying --cpu-affinity has no effect.
The arg will be ignored and he default affinity will be used. This has not been
tested either so if anyone has the ability to test it please do so and report.

There are no new 4way algos this release but optiizing shavite came as a surprise
and helps all CPUs with AES.

The past two releases have also seen some reworking of some existing SIMD code as
I learn new techniques. It should be more efficient but not likely to produce a significant
speed up.

There are currently 2 4way blockers. BMW is blocking full optimization of x11 and blake256
is blocking m7m. I'd like to get those resolved but I'm stuck at the moment. Since m7m is
CPU only I'd like to prioritize that algo.

A few algos have 4way enabled bur are either untested or have known problems that affect
performance.

Tested working: skein, keccak, keccakc, nist5, tribus.

Enabled untested: skein2, jha, whirlpool, pentablake.

Enabled with known problems: blake256 lane corruption: lyra2z, decred, blake.
These algos operate in 2way mode due to invalid hash in 2 lanes.

[My9bot]

Code:

         **********  cpuminer-opt 3.7.6  ***********
     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-5010U CPU @ 2.10GHz.
SW built on Dec 15 2017 with GCC 6.3.0.
CPU features: SSE2 AES AVX AVX2.
SW features: SSE2 AES AVX AVX2 4WAY.
Algo features: AVX AVX2.
Start mining with AVX2.

[2017-12-15 05:13:05] Starting Stratum on stratum+tcp://pool.hppcoin.com:3888
[2017-12-15 05:13:05] 4 miner threads started, using 'lyra2h' algorithm.
[2017-12-15 05:13:06] Stratum difficulty set to 0.03
[2017-12-15 05:14:57] lyra2h block 3745, diff 1.086
[2017-12-15 05:15:00] CPU #2: 33.13 kH, 304.87 H/s
[2017-12-15 05:15:01] CPU #1: 31.07 kH, 284.39 H/s
[2017-12-15 05:15:01] CPU #3: 33.19 kH, 303.82 H/s
[2017-12-15 05:15:01] CPU #0: 29.41 kH, 269.21 H/s
[2017-12-15 05:15:57] CPU #2: 18.29 kH, 320.96 H/s
[2017-12-15 05:15:58] CPU #1: 17.06 kH, 299.32 H/s
[2017-12-15 05:15:59] CPU #0: 16.15 kH, 277.56 H/s
[2017-12-15 05:15:59] CPU #3: 18.23 kH, 313.18 H/s
[2017-12-15 05:16:59] CPU #2: 19.26 kH, 311.88 H/s
[2017-12-15 05:17:00] CPU #1: 17.96 kH, 285.40 H/s
[2017-12-15 05:17:00] CPU #0: 16.65 kH, 269.79 H/s
[2017-12-15 05:17:00] CPU #3: 18.79 kH, 304.49 H/s
[2017-12-15 05:17:29] 4 WAY hash nonces submitted: 0
[2017-12-15 05:17:29] 1 WAY hash nonce submitted
[2017-12-15 05:17:29] CPU #1: 8271 H, 290.19 H/s
[2017-12-15 05:17:29] Rejected 1/1 (100.0%), 62.97 kH, 1176.35 H/s
[2017-12-15 05:17:29] reject reason: low difficulty share of 1.1898710488783548e-7
[2017-12-15 05:17:29] factor reduced to : 0.67
[2017-12-15 05:17:46] CPU #3: 18.27 kH, 400.63 H/s
[2017-12-15 05:17:46] CPU #0: 16.19 kH, 354.79 H/s
[2017-12-15 05:17:46] CPU #2: 18.71 kH, 393.31 H/s
[2017-12-15 05:17:47] CPU #1: 17.41 kH, 944.91 H/s
[2017-12-15 05:17:48] 4 WAY hash nonces submitted: 0
[2017-12-15 05:17:48] 1 WAY hash nonce submitted
[2017-12-15 05:17:48] CPU #2: 9619 H, 7518.31 H/s
[2017-12-15 05:17:48] Rejected 2/2 (100.0%), 61.49 kH, 9218.64 H/s
[2017-12-15 05:17:48] reject reason: low difficulty share of 1.0869699425015301e-7
[2017-12-15 05:17:48] factor reduced to : 0.44
[2017-12-15 05:17:48] CPU #0: 21.29 kH, 9075.46 H/s
[2017-12-15 05:17:49] CPU #3: 24.04 kH, 9621.84 H/s
[2017-12-15 05:17:54] CPU #1: 56.70 kH, 8476.80 H/s
[2017-12-15 05:17:55] 4 WAY hash nonces submitted: 0
[2017-12-15 05:17:55] 1 WAY hash nonce submitted
[2017-12-15 05:17:55] CPU #2: 62.99 kH, 8803.87 H/s
[2017-12-15 05:17:55] Rejected 3/3 (100.0%), 165.01 kH, 35.98 kH/s
[2017-12-15 05:17:55] reject reason: low difficulty share of 3.9760953496518064e-8
[2017-12-15 05:17:55] factor reduced to : 0.30
[2017-12-15 05:17:55] 4 WAY hash nonces submitted: 0
[2017-12-15 05:17:55] 1 WAY hash nonce submitted
[2017-12-15 05:17:55] CPU #1: 10.24 kH, 14.97 kH/s
[2017-12-15 05:17:55] Rejected 4/4 (100.0%), 118.56 kH, 42.48 kH/s
[2017-12-15 05:17:55] reject reason: low difficulty share of 7.469801103230193e-7
[2017-12-15 05:17:55] factor reduced to : 0.20
[2017-12-15 05:18:03] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:03] 1 WAY hash nonce submitted
[2017-12-15 05:18:03] CPU #3: 167.92 kH, 11.32 kH/s
[2017-12-15 05:18:03] Rejected 5/5 (100.0%), 262.44 kH, 44.17 kH/s
[2017-12-15 05:18:03] reject reason: low difficulty share of 3.4403911449252514e-8
[2017-12-15 05:18:03] factor reduced to : 0.13
[2017-12-15 05:18:14] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:14] 1 WAY hash nonce submitted
[2017-12-15 05:18:14] CPU #0: 222.08 kH, 8624.82 H/s
[2017-12-15 05:18:14] Rejected 6/6 (100.0%), 463.24 kH, 43.72 kH/s
[2017-12-15 05:18:14] reject reason: low difficulty share of 8.317881954690417e-8
[2017-12-15 05:18:14] factor reduced to : 0.09
[2017-12-15 05:18:14] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:15] 1 WAY hash nonce submitted
[2017-12-15 05:18:15] CPU #0: 3528 H, 13.74 kH/s
[2017-12-15 05:18:15] Rejected 7/7 (100.0%), 244.68 kH, 48.84 kH/s
[2017-12-15 05:18:15] reject reason: low difficulty share of 8.689102139919432e-8
[2017-12-15 05:18:15] factor reduced to : 0.06
[2017-12-15 05:18:15] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:15] 1 WAY hash nonce submitted
[2017-12-15 05:18:15] CPU #0: 431 H, 7178.07 H/s
[2017-12-15 05:18:15] Rejected 8/8 (100.0%), 241.58 kH, 42.27 kH/s
[2017-12-15 05:18:15] reject reason: low difficulty share of 1.0635928005429685e-7
[2017-12-15 05:18:15] factor reduced to : 0.04
[2017-12-15 05:18:18] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:18] 1 WAY hash nonce submitted
[2017-12-15 05:18:18] CPU #2: 222.20 kH, 9596.46 H/s
[2017-12-15 05:18:18] Rejected 9/9 (100.0%), 400.79 kH, 43.06 kH/s
[2017-12-15 05:18:18] reject reason: low difficulty share of 7.515368302351459e-8
[2017-12-15 05:18:18] factor reduced to : 0.03
[2017-12-15 05:18:40] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:40] 1 WAY hash nonce submitted
[2017-12-15 05:18:40] CPU #0: 279.30 kH, 10.96 kH/s
[2017-12-15 05:18:40] Rejected 10/10 (100.0%), 679.66 kH, 46.84 kH/s
[2017-12-15 05:18:40] reject reason: low difficulty share of 5.0051796485619505e-8
[2017-12-15 05:18:40] factor reduced to : 0.02
[2017-12-15 05:18:46] CPU #3: 678.93 kH, 16.04 kH/s
[2017-12-15 05:18:54] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:54] 1 WAY hash nonce submitted
[2017-12-15 05:18:54] CPU #2: 536.56 kH, 15.03 kH/s
[2017-12-15 05:18:54] Rejected 11/11 (100.0%), 1505.03 kH, 57.00 kH/s
[2017-12-15 05:18:54] reject reason: low difficulty share of 9.10089396836757e-8
[2017-12-15 05:18:54] factor reduced to : 0.01
[2017-12-15 05:18:57] Stratum difficulty set to 0.0171429
[2017-12-15 05:21:04] CPU #1: 898.44 kH, 4757.21 H/s

[joblo]

Code:

         **********  cpuminer-opt 3.7.6  ***********
     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-5010U CPU @ 2.10GHz.
SW built on Dec 15 2017 with GCC 6.3.0.
CPU features: SSE2 AES AVX AVX2.
SW features: SSE2 AES AVX AVX2 4WAY.
Algo features: AVX AVX2.
Start mining with AVX2.

[2017-12-15 05:13:05] Starting Stratum on stratum+tcp://pool.hppcoin.com:3888
[2017-12-15 05:13:05] 4 miner threads started, using 'lyra2h' algorithm.
[2017-12-15 05:13:06] Stratum difficulty set to 0.03
[2017-12-15 05:14:57] lyra2h block 3745, diff 1.086
[2017-12-15 05:15:00] CPU #2: 33.13 kH, 304.87 H/s
[2017-12-15 05:15:01] CPU #1: 31.07 kH, 284.39 H/s
[2017-12-15 05:15:01] CPU #3: 33.19 kH, 303.82 H/s
[2017-12-15 05:15:01] CPU #0: 29.41 kH, 269.21 H/s
[2017-12-15 05:15:57] CPU #2: 18.29 kH, 320.96 H/s
[2017-12-15 05:15:58] CPU #1: 17.06 kH, 299.32 H/s
[2017-12-15 05:15:59] CPU #0: 16.15 kH, 277.56 H/s
[2017-12-15 05:15:59] CPU #3: 18.23 kH, 313.18 H/s
[2017-12-15 05:16:59] CPU #2: 19.26 kH, 311.88 H/s
[2017-12-15 05:17:00] CPU #1: 17.96 kH, 285.40 H/s
[2017-12-15 05:17:00] CPU #0: 16.65 kH, 269.79 H/s
[2017-12-15 05:17:00] CPU #3: 18.79 kH, 304.49 H/s
[2017-12-15 05:17:29] 4 WAY hash nonces submitted: 0
[2017-12-15 05:17:29] 1 WAY hash nonce submitted
[2017-12-15 05:17:29] CPU #1: 8271 H, 290.19 H/s
[2017-12-15 05:17:29] Rejected 1/1 (100.0%), 62.97 kH, 1176.35 H/s
[2017-12-15 05:17:29] reject reason: low difficulty share of 1.1898710488783548e-7
[2017-12-15 05:17:29] factor reduced to : 0.67
[2017-12-15 05:17:46] CPU #3: 18.27 kH, 400.63 H/s
[2017-12-15 05:17:46] CPU #0: 16.19 kH, 354.79 H/s
[2017-12-15 05:17:46] CPU #2: 18.71 kH, 393.31 H/s
[2017-12-15 05:17:47] CPU #1: 17.41 kH, 944.91 H/s
[2017-12-15 05:17:48] 4 WAY hash nonces submitted: 0
[2017-12-15 05:17:48] 1 WAY hash nonce submitted
[2017-12-15 05:17:48] CPU #2: 9619 H, 7518.31 H/s
[2017-12-15 05:17:48] Rejected 2/2 (100.0%), 61.49 kH, 9218.64 H/s
[2017-12-15 05:17:48] reject reason: low difficulty share of 1.0869699425015301e-7
[2017-12-15 05:17:48] factor reduced to : 0.44
[2017-12-15 05:17:48] CPU #0: 21.29 kH, 9075.46 H/s
[2017-12-15 05:17:49] CPU #3: 24.04 kH, 9621.84 H/s
[2017-12-15 05:17:54] CPU #1: 56.70 kH, 8476.80 H/s
[2017-12-15 05:17:55] 4 WAY hash nonces submitted: 0
[2017-12-15 05:17:55] 1 WAY hash nonce submitted
[2017-12-15 05:17:55] CPU #2: 62.99 kH, 8803.87 H/s
[2017-12-15 05:17:55] Rejected 3/3 (100.0%), 165.01 kH, 35.98 kH/s
[2017-12-15 05:17:55] reject reason: low difficulty share of 3.9760953496518064e-8
[2017-12-15 05:17:55] factor reduced to : 0.30
[2017-12-15 05:17:55] 4 WAY hash nonces submitted: 0
[2017-12-15 05:17:55] 1 WAY hash nonce submitted
[2017-12-15 05:17:55] CPU #1: 10.24 kH, 14.97 kH/s
[2017-12-15 05:17:55] Rejected 4/4 (100.0%), 118.56 kH, 42.48 kH/s
[2017-12-15 05:17:55] reject reason: low difficulty share of 7.469801103230193e-7
[2017-12-15 05:17:55] factor reduced to : 0.20
[2017-12-15 05:18:03] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:03] 1 WAY hash nonce submitted
[2017-12-15 05:18:03] CPU #3: 167.92 kH, 11.32 kH/s
[2017-12-15 05:18:03] Rejected 5/5 (100.0%), 262.44 kH, 44.17 kH/s
[2017-12-15 05:18:03] reject reason: low difficulty share of 3.4403911449252514e-8
[2017-12-15 05:18:03] factor reduced to : 0.13
[2017-12-15 05:18:14] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:14] 1 WAY hash nonce submitted
[2017-12-15 05:18:14] CPU #0: 222.08 kH, 8624.82 H/s
[2017-12-15 05:18:14] Rejected 6/6 (100.0%), 463.24 kH, 43.72 kH/s
[2017-12-15 05:18:14] reject reason: low difficulty share of 8.317881954690417e-8
[2017-12-15 05:18:14] factor reduced to : 0.09
[2017-12-15 05:18:14] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:15] 1 WAY hash nonce submitted
[2017-12-15 05:18:15] CPU #0: 3528 H, 13.74 kH/s
[2017-12-15 05:18:15] Rejected 7/7 (100.0%), 244.68 kH, 48.84 kH/s
[2017-12-15 05:18:15] reject reason: low difficulty share of 8.689102139919432e-8
[2017-12-15 05:18:15] factor reduced to : 0.06
[2017-12-15 05:18:15] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:15] 1 WAY hash nonce submitted
[2017-12-15 05:18:15] CPU #0: 431 H, 7178.07 H/s
[2017-12-15 05:18:15] Rejected 8/8 (100.0%), 241.58 kH, 42.27 kH/s
[2017-12-15 05:18:15] reject reason: low difficulty share of 1.0635928005429685e-7
[2017-12-15 05:18:15] factor reduced to : 0.04
[2017-12-15 05:18:18] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:18] 1 WAY hash nonce submitted
[2017-12-15 05:18:18] CPU #2: 222.20 kH, 9596.46 H/s
[2017-12-15 05:18:18] Rejected 9/9 (100.0%), 400.79 kH, 43.06 kH/s
[2017-12-15 05:18:18] reject reason: low difficulty share of 7.515368302351459e-8
[2017-12-15 05:18:18] factor reduced to : 0.03
[2017-12-15 05:18:40] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:40] 1 WAY hash nonce submitted
[2017-12-15 05:18:40] CPU #0: 279.30 kH, 10.96 kH/s
[2017-12-15 05:18:40] Rejected 10/10 (100.0%), 679.66 kH, 46.84 kH/s
[2017-12-15 05:18:40] reject reason: low difficulty share of 5.0051796485619505e-8
[2017-12-15 05:18:40] factor reduced to : 0.02
[2017-12-15 05:18:46] CPU #3: 678.93 kH, 16.04 kH/s
[2017-12-15 05:18:54] 4 WAY hash nonces submitted: 0
[2017-12-15 05:18:54] 1 WAY hash nonce submitted
[2017-12-15 05:18:54] CPU #2: 536.56 kH, 15.03 kH/s
[2017-12-15 05:18:54] Rejected 11/11 (100.0%), 1505.03 kH, 57.00 kH/s
[2017-12-15 05:18:54] reject reason: low difficulty share of 9.10089396836757e-8
[2017-12-15 05:18:54] factor reduced to : 0.01
[2017-12-15 05:18:57] Stratum difficulty set to 0.0171429
[2017-12-15 05:21:04] CPU #1: 898.44 kH, 4757.21 H/s

Stupid mistake, try this change in algo/lyra2/lyra2h.c line 34:

Code:

34c34
<         LYRA2Z( lyra2h_matrix, hash, 32, hash, 32, hash, 32, 16, 16, 16 );
---
>         LYRA2Z( lyra2h_matrix, hash, 32, hash, 32, hash, 32, 8, 8, 8);

[mangoo]

Has anyone tried to compile cpuminer-opt on ARM architecture? I've tried, but it fails miserably...

[joblo]

Has anyone tried to compile cpuminer-opt on ARM architecture? I've tried, but it fails miserably...

Optimizations are architecture specific meaning that all optimizations would have to be
rewritten for ARM. That's the nature of specialization. As it stands now cpuminer-opt
already contains 3 or 4 versions of many functions just to suppport the variations within
the x86_64 architecture.

An optimized ARM miner would essentially have to have rewritten all optimizations I imported as well
as the ones I've added over the past 2 years. This would require a very skilled, and highly paid,
ARM developper.

Your best bet for ARM at this time is an unoptimized miner that isn't tied to one specific arcitecture.

[mangoo]

https://www.scaleway.com/

They have 3 EUR / month ARM servers with 4 CPU cores.

So I was wondering how good or bad they perform.

[joblo]

Mining with ARM is used mostly by web servers to mine coins using the CPUs of visitors'
phones and tablets, either with or without their knowledge.

Some people collect large numbers of old phones and use them for mining with the batteries removed.

But mining with individual phones or tablets (or any "low power" device with a battery) just isn't feasible.
Performance is crippled and it will shorten the life span of the device due to heat and battery wear, not
to mention the risk of lithium flameout.

There might be a business case for clustering large numbers of ARM CPUs to build a highly efficient
low power compute platform but that efficiency depends on the efficiency of the software.

[Mr.merson]

Has anyone tried to compile cpuminer-opt on ARM architecture? I've tried, but it fails miserably...

Optimizations are architecture specific meaning that all optimizations would have to be
rewritten for ARM. That's the nature of specialization. As it stands now cpuminer-opt
already contains 3 or 4 versions of many functions just to suppport the variations within
the x86_64 architecture.

An optimized ARM miner would essentially have to have rewritten all optimizations I imported as well
as the ones I've added over the past 2 years. This would require a very skilled, and highly paid,
ARM developper.

Your best bet for ARM at this time is an unoptimized miner that isn't tied to one specific arcitecture.

Does this also apply forgotten NVIDIA tesla architecture?

I would like to at least make the attempt,but I'm a newbie to what programming language refers,there are also no guides on how to work from 0 or how to start

my question although a bit vague, it is possible to work old and new some algorithms such as "cryptonight" ,has some impediment to what it refers to level of instructions or obstacle? (I know that this is not the indicated site I only ask for opinions regarding this)

Any opinion is appreciated 

[mangoo]

I've tried running cpuminer-opt 3.7.6 with lyra2z on a 48 CPU system - unfortunately, only 32 CPUs are used.

The program says "48 miner threads started, using 'lyra2z' algorithm", with or without -t 48 option.

cpuminer-opt 3.7.3 behaves correctly and runs on all 48 cores.