Topic: New demonstration CPU miner available - page 8. (Read 386323 times)

Hi. I've made some minor modifications to cpuminer that are x86_64 linux specific.

Here's the list of changes:
- Linux x86_64 tweaked version
- Uses sse2_64 algo by default
- Detects CPUs and sets threads accordingly
- Uses CPU affinity for each thread where appropriate
- Sets scheduling policy to lowest possible
- Minor performance tweaks

The changes aren't entirely portable but Jeff you might be interested in some or all of them.

Grab the source here:
http://ck.kolivas.org/apps/cpuminer-1.0.1a.tar.bz2

Running into this problem:

make  all-recursive
make[1]: Entering directory `/home/d337z/Desktop/bitcoin-cpuminer'
Making all in compat
make[2]: Entering directory `/home/d337z/Desktop/bitcoin-cpuminer/compat'
make[3]: Entering directory `/home/d337z/Desktop/bitcoin-cpuminer/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/d337z/Desktop/bitcoin-cpuminer/compat'
make[2]: Leaving directory `/home/d337z/Desktop/bitcoin-cpuminer/compat'
Making all in x86_64
make[2]: Entering directory `/home/d337z/Desktop/bitcoin-cpuminer/x86_64'
/usr/bin/yasm -f elf64 sha256_xmm_amd64.asm
rm -f libx8664.a
ar cru libx8664.a sha256_xmm_amd64.o
ranlib libx8664.a
make[2]: Leaving directory `/home/d337z/Desktop/bitcoin-cpuminer/x86_64'
make[2]: Entering directory `/home/d337z/Desktop/bitcoin-cpuminer'
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing    -DHAS_YASM -march=native -O3 -pipe -fomit-frame-pointer -Wall -MT cpu-miner.o -MD -MP -MF .deps/cpu-miner.Tpo -c -o cpu-miner.o cpu-miner.c
cpu-miner.c: In function ‘parse_arg’:
cpu-miner.c:726:3: warning: passing argument 2 of ‘json_load_file’ makes integer from pointer without a cast
/usr/local/include/jansson.h:221:9: note: expected ‘size_t’ but argument is of type ‘struct json_error_t *’
cpu-miner.c:726:3: error: too few arguments to function ‘json_load_file’
/usr/local/include/jansson.h:221:9: note: declared here
make[2]: *** [cpu-miner.o] Error 1
make[2]: Leaving directory `/home/d337z/Desktop/bitcoin-cpuminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/d337z/Desktop/bitcoin-cpuminer'
make: *** [all] Error 2


I configured with -march=native (Core2) -O3 -pipe -fomit-frame-pointer -Wall.  With -mtune and -mcpu, I get the exact same errors.  Could someone tell me what's going wrong here?  I'm on Ubuntu 11.04 trying to compile this.  I've also tried removing yasm as a means to mitigate against any common errors that may exist between Ubuntu and Mac's setups. So far, no good.

Just for the record, with minerd 1.0.1 I get:

Intel(R) Core(TM) i3 CPU M350 @2.27GHz:
790 khash/s/core with 4way (actually running at 930 MHz due to high temperature).

Intel(R) Xeon(R) CPU E5420 @2.50GHz:
1680 khash/s/core with sse2_64.

Quad-Core AMD Opteron(tm) Processor 2376:
2480 khash/s/core with 4way.

Intel(R) Xeon(TM) CPU 3.00GHz:
630 khash/s/core with sse2_64.

Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz:
1220 khash/s/core with 4way (yasm is too old in this machine to have sse2_64).


Edit: added Xeon 3GHz and i3 2.93GHz

Anyone having any luck with this miner on Vista? When I try to run it from the command line, I get the whole "minerd.exe has stopped working"

UAC is off and I've tried running as an Administrator.

Any ideas? Thanks.

Hello, this is a great CPU miner, which succesfully runs on my server.
Now I am trying to get it working on my old PowerPC Mac (G5) with Mac OS X 10.5.
It compiles fine and runs but it seems the calculations  come out wrong.
What could it be? (Im a programmer but not familiar with c/c++).

Error messages:

Could you please explain how to do this?

The download links work just fine, from multiple locations.

Download links not working for me... can some one upload to rapidshare or sth? tnx

OK I got it now. Writing
in the config.json file, makes it write in the system log file, with it set to 'false' writes the output in the 'standard error'.

Sorry for the little confusion I made. 

If someone knows something about the docu ... appreciated!

Since it's measuring in khash/s, and there is a huge variance compared to the overhead, you wouldn't notice unless you started a *really* large amount of threads.

I kinda assumed you'd know this, but how about?:
(IOW, whether the output is on stderr or stdout is somewhat of an arbitrary choice, and redirecting is a non-job, anyway; why bother handling another special case just for this? Anyhow, this sort of question is really easily handled by a look into the code, even I understand most of it )

This is why I shouldn't answer such a long post less than 5 minutes before I have to leave...
That info came from some sort of discussion around long polling, but I can't for the life of me remember where exactly. Sorry, and I hope the answer was somewhat helpful, anyway.

Thanks for quick response!!!

Hmmm, I can't confirm this. I experienced around increasing and decreasing the amount of thread and came to the conclusion that the highest sum of hash rate I get with 10 threads, although my server is running at full speed with only 2 threads already.

If I write nothing it will be send to standard error not standard output!!! So what do I write if I want it to standard output (it's a file in my case)?

Where is it? I only red the 'help'.

Creating and maintaining a thread has a (pretty small) overhead, so for every thread you create, your mining is getting a tiny bit slower. I don't think setting the amount of threads to higher than the amount of logical cores (or perhaps logical cores + 1) is very useful.

Nothing - it'll be printed to standard output when syslog isn't set. (Also, messing with stuff you don't understand is generally not advisable - did you read the help output properly?)

I've noticed those, too. Apparently the claim that all config options are also supported in the JSON config file is false.

Hmm, again: read the docu?
Basically, there are two conflicting criteria by which minerd can stop working on the current work unit:

• when a timeout occurs while searching for a share
• when the server sends new work via the long polling spec

The first criterion is used when the server doesn't support long polling or if it's manually disabled via the config, otherwise the second is used.

Hi!

1. can you tell me what is the difference running 10 threads or 100? The hash-rate is not significantly different using 10 or 100 (in the sum of all threads of each).

2. I use the config.json file as follows.

2.1. What can I write into to the value of 'syslog' (see "_comment9a" at the moment) if I want to send it to "standard output"?
2.1. Is the value 'false' correct? It runs, but I get the following output (using 'off' doesn't work):

3. Can you please tell me the exact function of 'scantime'? It looks that it only makes a difference when setting 'no-longpoll' to true!?!

Thanks and regards

deti

I'm pretty sure the url argument needs a protocol set, so try
The thread for your pool might provide more concrete details, like the exact command line you need to run.

I added :8332 and it worked (and I changed my pw so that one I posted won't work)

Hi,

I downloaded the 1.0 Windows binary installer.

No matter what options I set, it gives me the help message


Is this a bug?

Or did I miss something?

It looks to me like you're getting an HTML response instead of a JSON one. Something to ask your pool admin about (or double-check the URL you're passing, especially if the pool doesn't use the standard port).

I don't understand what this means. I get this with the default algo too.

Well, just because sha256_sse2_amd64.o is being linked in doesn't mean it will be available as an algorithm (it's basically a dummy object if it doesn't think it can be compiled). You could try adding "-DWANT_X8664_SSE2" to CFLAGS to see whether that helps/produces an error that will help you track this down.
Looking at miner.h, it seems like the only dependencies are a 64-bit environment, SSE2 and yasm, though, so you may want to double-check the output of configure...

If you run:
Do you see any output? It seems to work for me on my 10.10.