Topic: Wolf's XMR/BCN/DSH CPUMiner - 2x speed compared to LucasJones' - NEW 06/20/2014 - page 8. (Read 547084 times)

Beware!

CPUminer is an Trojan!

Hi all,
I have a question regarding mining XMR : Can I mining XMR with Pi3 and USB Miner ?

trying to compile for win 64 bit
with this instruction
https://bitcointalksearch.org/topic/m.6542760
tried many different ./configure
everytime it success compile but the compiled binary crash while trying to run also i tried to strip the exe too 

Thanks for the response..  not too long after I took that shot I started getting stratum errors....  shut it down for now, will play with it tonight.

edit: btw.  I have a phenom 6 core on that rig.. should run pretty good.  thxs again.

looks like you haven't had any shares accepted so you don't see the speed.  I see that you started at a diff of 5000 and the miner keeps reducing the diff because it's too high.  Eventually it will adjust but you should start with a port with a lower diff as it seems you have a slow CPU for Monero.  There are pools that have lower starting diffs and http://mine.moneroworld.com/ has a slowly adjusting diff which is good for slow miners as the diff doesn't jump up which can cause time outs when the diff adjusts up too quickly.  If your CPU does not have AES-NI it will be slow.  Also note that you need 2MB of cache for each thread you run.  I have an i5 with 6MB cache and it works better with 2 of the 4 cores instead of 3 because the cache is shared.  I had an old pentium that was getting ~33 H/s and at that rate with present conditions it would take close to 5 months to mine 1 Monero

BTW when shares are accepted it will look like this:
[2016-09-30 09:58:44] accepted: 11482/11482 (100.00%), 90.50 H/s at diff 2643 (yay!!!)

You should also see something like this before shares are accepted:
[2016-09-30 10:00:33] thread 1: 2671 hashes, 43.15 H/s

just tried the cpu miner.. pretty sure it is working, but I dont see the speed.. is there a display setting to show hash amount?

This is a CPU mining thread, not GPU.

C:\install\xmr\cpuminer-multi-wolf-06-12-2014>minerd -a cryptonight -o stratum+tcp://monerohash.com:3333 -u mywallet -p x
[2016-09-30 08:08:10] Using JSON-RPC 2.0
[2016-09-30 08:08:10] Starting Stratum on stratum+tcp://monerohash.com:3333
[2016-09-30 08:08:10] 5 miner threads started, using 'cryptonight' algorithm.
[2016-09-30 08:08:10] Pool set diff to 5000
[2016-09-30 08:08:10] Stratum detected new block
[2016-09-30 08:10:38] Pool set diff to 3401
[2016-09-30 08:10:38] Stratum detected new block
[2016-09-30 08:13:08] Pool set diff to 2252
[2016-09-30 08:13:08] Stratum detected new block
[2016-09-30 08:13:59] Stratum detected new block
[2016-09-30 08:15:28] Stratum detected new block
[2016-09-30 08:15:39] Pool set diff to 1491
[2016-09-30 08:15:39] Stratum detected new block

Is there anybody who successfully compiled monero (wolf-cpu) miner ? 

Any pool you want to use has this in the getting started area.
And yes, you need to have a wallet for this, although, if you only make a short test you will not be able to withdraw, so any publicly available XMR address will do.

Hey guys,
Can someone share his minerd .bat file need to do some tests on a i7 980x , thanks in advance !

Btw.. Just thought i'd mention this:

Latest CPUMiner compiled from git: (24 x Intel(R) Xeon(R) CPU X5650 @ 2.67GHz)

Over a 20 minute duration:

[2014-08-02 20:25:25] accepted: 191/234 (81.62%), 230.74 H/s at diff 980 (yay!!!)
[2014-08-02 20:25:29] accepted: 192/235 (81.70%), 230.63 H/s at diff 980 (yay!!!)
[2014-08-02 20:25:29] accepted: 193/236 (81.78%), 230.61 H/s at diff 980 (yay!!!)
[2014-08-02 20:25:31] accepted: 194/237 (81.86%), 230.16 H/s at diff 980 (yay!!!)
[2014-08-02 20:25:40] accepted: 195/238 (81.93%), 231.01 H/s at diff 980 (yay!!!)

Then i removed all of the "optimizations" from the Makefile:

From:

am__append_3 = -Ofast -flto -fuse-linker-plugin -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerg
e-all-constants -fbranch-target-load-optimize2 -fsched2-use-superblocks -maes

to :

am__append_3 = -maes

The result?

[2014-08-02 20:26:44] accepted: 189/231 (81.82%), 289.83 H/s at diff 1384 (yay!!!)
[2014-08-02 20:26:45] accepted: 190/232 (81.90%), 290.09 H/s at diff 1384 (yay!!!)
[2014-08-02 20:27:03] accepted: 191/233 (81.97%), 291.41 H/s at diff 1384 (yay!!!)
[2014-08-02 20:27:07] accepted: 192/234 (82.05%), 290.47 H/s at diff 1384 (yay!!!)

There are numerous posts/warnings on-line about over-aggressive compile-time "optimizations".
Just thought I'd post my results/findings which concur.

Regards,
Cami