An (even more) optimized version of cpuminer (pooler's cpuminer, CPU-only)

[K1773R]

ahh durr my mistake, heres the CPU batch file command:

@echo off

START /LOW /B minerd.exe --algo scrypt --url http://mine.pool-x.eu:8337 --userpass klondike_bar.1:x --threads 4 -r -1 -s 5


its essentially the default configuration as im not sure how best to utilise my  i7 620m (2.67GHz)

Ive got it working now, but at ~3.2khash/core (~13 khash/s) it feels slower than what i would expect (i imagined 20+ khash/s)

-r -1 <-- dont specify this. dont set --threads too, so it uses all threads and maps each thread to a core (it does this on unix, dunno if this works in winblows). there is no need to set -s 5 too since this is default.

so just:   @echo off

START /LOW /B minerd.exe --algo scrypt --url http://mine.pool-x.eu:8337 --userpass klondike_bar.1:x

im running about 13.6 khash/s now, about an 8% increase. any other tweaks i should be aware of?

besides turning other applications off who hog the CPU no, the mining itself is made in ASM (Assembler) to get the full hashing power out of ur CPU.
13.6kH/s is acceptable fur such a crappy CPU
i got 57kH/s with a i7 2700k @ 5GHz overclocked and linux (makes a difference too)

[420]

3930k gets you 90khash if clocked right

[muqali]

3930k gets you 90khash if clocked right

I'd love to see what a quad socket 64 core Interlagos system would pull in. Not that it'd be efficient, a GPU would be far better, but just to see the numbers.

[420]

3930k gets you 90khash if clocked right

I'd love to see what a quad socket 64 core Interlagos system would pull in. Not that it'd be efficient, a GPU would be far better, but just to see the numbers.

64 core? link please. i search that only find 16 core

[pieppiep]

I think he means a quad socket system with 16 core cpu's for a total of 64 cores.

[420]

I think he means a quad socket system with 16 core cpu's for a total of 64 cores.

yeah get an $800 motherboard and what; $600 cpu's and a 1000 watt psu?

http://www.newegg.com/Product/Product.aspx?Item=N82E16813151219

[muqali]

I think he means a quad socket system with 16 core cpu's for a total of 64 cores.

That is indeed what I meant.

[muqali]

I think he means a quad socket system with 16 core cpu's for a total of 64 cores.

yeah get an $800 motherboard and what; $600 cpu's and a 1000 watt psu?

http://www.newegg.com/Product/Product.aspx?Item=N82E16813151219

the top end 16 core Interlagos is a bit more than 600 though. On the plus side, I've already got a LEPA 1600W power supply I don't need to buy.

[Pontius]

I'd love to see what a quad socket 64 core Interlagos system would pull in. Not that it'd be efficient, a GPU would be far better, but just to see the numbers.

Interlagos is basicly a set of Istanbul CPUs, so here - calc yourself. ;-)

Code:

$ cat /proc/cpuinfo |grep name  |uniq 
model name	: Six-Core AMD Opteron(tm) Processor 8439 SE
$ cat /proc/cpuinfo |grep processor |wc -l
48
$ minerd --version
cpuminer 2.2.3
libcurl/7.27.0 OpenSSL/1.0.1c zlib/1.2.3 c-ares/1.9.1
$ minerd --benchmark
[2013-01-28 08:13:28] 48 miner threads started, using 'scrypt' algorithm.
[2013-01-28 08:13:29] thread 4: 4104 hashes, 5.24 khash/s
[2013-01-28 08:13:29] thread 5: 4104 hashes, 5.23 khash/s
[2013-01-28 08:13:29] thread 3: 4104 hashes, 5.23 khash/s
[2013-01-28 08:13:29] thread 0: 4104 hashes, 5.22 khash/s
[2013-01-28 08:13:29] thread 11: 4104 hashes, 5.23 khash/s
[....]
[2013-01-28 08:13:34] Total: 252.92 khash/s
[....]
[2013-01-28 08:13:39] Total: 253.14 khash/s
[....]
[2013-01-28 08:13:44] Total: 253.00 khash/s
[....]
[2013-01-28 08:13:49] Total: 252.80 khash/s

(For sha256d those 48 cores do about 150 MH/s or ~3.125 MH/s per core)

[420]

I'd love to see what a quad socket 64 core Interlagos system would pull in. Not that it'd be efficient, a GPU would be far better, but just to see the numbers.

Interlagos is basicly a set of Istanbul CPUs, so here - calc yourself. ;-)

Code:

$ cat /proc/cpuinfo |grep name  |uniq 
model name	: Six-Core AMD Opteron(tm) Processor 8439 SE
$ cat /proc/cpuinfo |grep processor |wc -l
48
$ minerd --version
cpuminer 2.2.3
libcurl/7.27.0 OpenSSL/1.0.1c zlib/1.2.3 c-ares/1.9.1
$ minerd --benchmark
[2013-01-28 08:13:28] 48 miner threads started, using 'scrypt' algorithm.
[2013-01-28 08:13:29] thread 4: 4104 hashes, 5.24 khash/s
[2013-01-28 08:13:29] thread 5: 4104 hashes, 5.23 khash/s
[2013-01-28 08:13:29] thread 3: 4104 hashes, 5.23 khash/s
[2013-01-28 08:13:29] thread 0: 4104 hashes, 5.22 khash/s
[2013-01-28 08:13:29] thread 11: 4104 hashes, 5.23 khash/s
[....]
[2013-01-28 08:13:34] Total: 252.92 khash/s
[....]
[2013-01-28 08:13:39] Total: 253.14 khash/s
[....]
[2013-01-28 08:13:44] Total: 253.00 khash/s
[....]
[2013-01-28 08:13:49] Total: 252.80 khash/s

(For sha256d those 48 cores do about 150 MH/s or ~3.125 MH/s per core)

HAHAHAHA a 6 core, 12 virtual core 3930k does 90Kh/s

[scatha]

ermm.. you do CPU mining to utilize all the idle CPU power of your desktop PC don't you ? :O

[Rampion]

I'm trying to mine LTC on OSX, following all the instructions on the text file of the CPUMINER (minerd). When I run ./MINERD.sh I keep getting this error:

dyld: Library not loaded: /opt/local/lib/libidn.11.dylib
  Referenced from: /usr/bin/minerd
  Reason: image not found
./MINERD.sh: line 1: 12464 Trace/BPT trap: 5   

Could somebody give me a hand in order to solve this? I'm using Mountain Lion (10.8.2)

Thank you in advance.

[K1773R]

I'm trying to mine LTC on OSX, following all the instructions on the text file of the CPUMINER (minerd). When I run ./MINERD.sh I keep getting this error:

dyld: Library not loaded: /opt/local/lib/libidn.11.dylib
  Referenced from: /usr/bin/minerd
  Reason: image not found
./MINERD.sh: line 1: 12464 Trace/BPT trap: 5   

Could somebody give me a hand in order to solve this? I'm using Mountain Lion (10.8.2)

Thank you in advance.

it cant load the library libidn who should be at /opt/local/lib/libidn.11.dylib because it dosnt exist.
error reading is easy

[Rampion]

I'm trying to mine LTC on OSX, following all the instructions on the text file of the CPUMINER (minerd). When I run ./MINERD.sh I keep getting this error:

dyld: Library not loaded: /opt/local/lib/libidn.11.dylib
  Referenced from: /usr/bin/minerd
  Reason: image not found
./MINERD.sh: line 1: 12464 Trace/BPT trap: 5   

Could somebody give me a hand in order to solve this? I'm using Mountain Lion (10.8.2)

Thank you in advance.

it cant load the library libidn who should be at /opt/local/lib/libidn.11.dylib because it dosnt exist.
error reading is easy

I'm a newbie

Could you just let me know how to download/install the libidn library?

Thanks

[K1773R]

I'm trying to mine LTC on OSX, following all the instructions on the text file of the CPUMINER (minerd). When I run ./MINERD.sh I keep getting this error:

dyld: Library not loaded: /opt/local/lib/libidn.11.dylib
  Referenced from: /usr/bin/minerd
  Reason: image not found
./MINERD.sh: line 1: 12464 Trace/BPT trap: 5   

Could somebody give me a hand in order to solve this? I'm using Mountain Lion (10.8.2)

Thank you in advance.

it cant load the library libidn who should be at /opt/local/lib/libidn.11.dylib because it dosnt exist.
error reading is easy

I'm a newbie

Could you just let me know how to download/install the libidn library?

Thanks

no since i didnt google ur problem, nor am i a MacOSX user.
Even a newb can google, thats no excuse.

[Rampion]

I'm trying to mine LTC on OSX, following all the instructions on the text file of the CPUMINER (minerd). When I run ./MINERD.sh I keep getting this error:

dyld: Library not loaded: /opt/local/lib/libidn.11.dylib
  Referenced from: /usr/bin/minerd
  Reason: image not found
./MINERD.sh: line 1: 12464 Trace/BPT trap: 5   

Could somebody give me a hand in order to solve this? I'm using Mountain Lion (10.8.2)

Thank you in advance.

it cant load the library libidn who should be at /opt/local/lib/libidn.11.dylib because it dosnt exist.
error reading is easy

I'm a newbie

Could you just let me know how to download/install the libidn library?

Thanks

no since i didnt google ur problem, nor am i a MacOSX user.
Even a newb can google, thats no excuse.

I googled extensively and I couldn't find a solution - that's why I'm asking to the more experienced users in the forum. I wouldn't lose my time (and other's fellow bitcoiners time) asking in a forum if the answer was easily found googling the problem.

[datguywhowanders]

I actually encountered and fixed this last night. If you have Homebrew installed on your machine, just run:

brew install libidn

When it finishes, you may have to create some symbolic links to the library, but you'll have a copy on your machine at least.

[collaghost]

Hello, pooler! If there any chance to specify failover credentials in the miner itself? I'm aware of scripts index.php?topic=74941.0 and  index.php?topic=46.0  but I think this should be implemented in the miner itself in case if development is not halted.
Thanks for such a great miner.

[burnside]

Heads up all:

https://bitcointalk.org/index.php?topic=93540.msg1532516#msg1532516

The 64-bit cpuminer 2.2.3 windows binary in the zip file on the OP has been tampered with.  Unless you specify the username/password in a specific way, it will ignore your settings and instead use built-in creds.

Cheers.

[pooler]

Heads up all:

https://bitcointalk.org/index.php?topic=93540.msg1532516#msg1532516

The 64-bit cpuminer 2.2.3 windows binary in the zip file on the OP has been tampered with.  Unless you specify the username/password in a specific way, it will ignore your settings and instead use built-in creds.

Cheers.

burside, thank you very much for letting me know. I must have uploaded the wrong binary for the 64-bit Windows version of the miner. That version was compiled for internal use only, and never intended for public distribution. On the up side, that default address would never have worked from the outside of the private network it referred to, and when mining in a pool people notice immediately if shares don't show up in their account, so the only problem this could have caused is that getting the binary to work was trickier because you had to use the --userpass option instead of --user and --pass.

Unfortunately I'm currently away, so I'm unable to recompile the binary, but luckily there's not much difference between 2.2.2 and 2.2.3 apart from the benchmark feature, so for the moment people can just download version 2.2.2, which on Windows should not be any slower.

Miners who are currently using the "wrong" 64-bit 2.2.3 binary with no issues need not downgrade. There is no risk that your shares go to the wrong server or account, it's just that when you first set the miner up it may be a bit trickier to get your credentials to work, as in that binary not all of the command-line options for setting the credentials work as expected.