[ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 114.

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: cryptopie1 on January 22, 2017, 03:36:15 PM

So I'm trying to compile cpuminer-opt-3.4.12.tar.gz with ./build.sh in Debian 8.6 (jessie) system with a old Intel(R) Celeron(R) CPU 3.06GHz (SSE2 support only) but I got this error:

Code:

...
In file included from algo/nist5.c:17:0:
./algo/jh/sse2/jh_sse2_opt64.h:240:13: warning: ‘jhF8’ defined but not used [-Wunused-function]
 static void jhF8(jhState *state)
             ^
mv -f algo/.deps/cpuminer-m7m.Tpo algo/.deps/cpuminer-m7m.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I.  -Iyes/include -fno-strict-aliasing  -I. -Iyes/include -Wno-pointer-sign -Wno-pointer-to-int-cast   -O3 -march=native -Wall  -Iyes/include -MT algo/cpuminer-scrypt.o -MD -MP -MF algo/.deps/cpuminer-scrypt.Tpo -c -o algo/cpuminer-scrypt.o `test -f 'algo/scrypt.c' || echo './'`algo/scrypt.c
algo/scrypt.c: In function ‘register_scrypt_algo’:
algo/scrypt.c:783:36: error: ‘scrypt_1024_1_1_256_24way’ undeclared (first use in this function)
   gate->hash             = (void*)&scrypt_1024_1_1_256_24way;
                                    ^
algo/scrypt.c:783:36: note: each undeclared identifier is reported only once for each function it appears in
In file included from algo/scrypt.c:30:0:
algo/scrypt.c: At top level:
./miner.h:528:20: warning: ‘algo_names’ defined but not used [-Wunused-variable]
 static const char *algo_names[] = {
                    ^
algo/scrypt.c: In function ‘register_scrypt_algo’:
algo/scrypt.c:792:1: warning: control reaches end of non-void function [-Wreturn-type]
 };
 ^
Makefile:2934: recipe for target 'algo/cpuminer-scrypt.o' failed
make[2]: *** [algo/cpuminer-scrypt.o] Error 1
make[2]: ** Esperando que outros processos terminem.
mv -f algo/.deps/cpuminer-pluck.Tpo algo/.deps/cpuminer-pluck.Po
mv -f algo/.deps/cpuminer-neoscrypt.Tpo algo/.deps/cpuminer-neoscrypt.Po
mv -f algo/.deps/cpuminer-nist5.Tpo algo/.deps/cpuminer-nist5.Po
make[2]: Leaving directory '/home/cryptopie/cpuminer-opt-3.4.12'
Makefile:3517: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/cryptopie/cpuminer-opt-3.4.12'
Makefile:665: recipe for target 'all' failed
make: *** [all] Error 2
strip: 'cpuminer': No such file

I just want to mine Monero w/SSE2, some help please.
Thanks

How old is your CPU? It needs to be 64 bit.

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: emanymton on January 22, 2017, 03:33:18 PM

algo/hodl/hodl.cpp:96:18: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
EVP_CIPHER_CTX ctx;
^~~

It looks like a problem with an included library, to be specific. Probably a missing package.

cryptopie1

newbie

Activity: 2

Merit: 0

So I'm trying to compile cpuminer-opt-3.4.12.tar.gz with ./build.sh in Debian 8.6 (jessie) system with a old Intel(R) Celeron(R) CPU 3.06GHz (SSE2 support only) but I got this error:

Code:

...
In file included from algo/nist5.c:17:0:
./algo/jh/sse2/jh_sse2_opt64.h:240:13: warning: ‘jhF8’ defined but not used [-Wunused-function]
 static void jhF8(jhState *state)
             ^
mv -f algo/.deps/cpuminer-m7m.Tpo algo/.deps/cpuminer-m7m.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I.  -Iyes/include -fno-strict-aliasing  -I. -Iyes/include -Wno-pointer-sign -Wno-pointer-to-int-cast   -O3 -march=native -Wall  -Iyes/include -MT algo/cpuminer-scrypt.o -MD -MP -MF algo/.deps/cpuminer-scrypt.Tpo -c -o algo/cpuminer-scrypt.o `test -f 'algo/scrypt.c' || echo './'`algo/scrypt.c
algo/scrypt.c: In function ‘register_scrypt_algo’:
algo/scrypt.c:783:36: error: ‘scrypt_1024_1_1_256_24way’ undeclared (first use in this function)
   gate->hash             = (void*)&scrypt_1024_1_1_256_24way;
                                    ^
algo/scrypt.c:783:36: note: each undeclared identifier is reported only once for each function it appears in
In file included from algo/scrypt.c:30:0:
algo/scrypt.c: At top level:
./miner.h:528:20: warning: ‘algo_names’ defined but not used [-Wunused-variable]
 static const char *algo_names[] = {
                    ^
algo/scrypt.c: In function ‘register_scrypt_algo’:
algo/scrypt.c:792:1: warning: control reaches end of non-void function [-Wreturn-type]
 };
 ^
Makefile:2934: recipe for target 'algo/cpuminer-scrypt.o' failed
make[2]: *** [algo/cpuminer-scrypt.o] Error 1
make[2]: ** Esperando que outros processos terminem.
mv -f algo/.deps/cpuminer-pluck.Tpo algo/.deps/cpuminer-pluck.Po
mv -f algo/.deps/cpuminer-neoscrypt.Tpo algo/.deps/cpuminer-neoscrypt.Po
mv -f algo/.deps/cpuminer-nist5.Tpo algo/.deps/cpuminer-nist5.Po
make[2]: Leaving directory '/home/cryptopie/cpuminer-opt-3.4.12'
Makefile:3517: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/cryptopie/cpuminer-opt-3.4.12'
Makefile:665: recipe for target 'all' failed
make: *** [all] Error 2
strip: 'cpuminer': No such file

I just want to mine Monero w/SSE2, some help please.
Thanks

emanymton

full member

Activity: 219

Merit: 106

hello i am trying to build in kalilinux,
i am getting this error:
++ -DHAVE_CONFIG_H -I. -Iyes/include -fno-strict-aliasing -I./compat/jansson -I. -Iyes/include -O3 -march=native -Wall -std=gnu++11 -MT algo/hodl/cpuminer-hodl_arith_uint256.o -MD -MP -MF algo/hodl/.deps/cpuminer-hodl_arith_uint256.Tpo -c -o algo/hodl/cpuminer-hodl_arith_uint256.o `test -f 'algo/hodl/hodl_arith_uint256.cpp' || echo './'`algo/hodl/hodl_arith_uint256.cpp
algo/hodl/hodl.cpp: In function ‘int scanhash_hodl(int, work*, uint32_t, uint64_t*)’:
algo/hodl/hodl.cpp:96:18: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
EVP_CIPHER_CTX ctx;
^~~
In file included from algo/hodl/hodl.cpp:1:0:
./miner.h: At global scope:
./miner.h:529:20: warning: ‘algo_names’ defined but not used [-Wunused-variable]
static const char *algo_names[] = {
^~~~~~~~~~
Makefile:3317: recipe for target 'algo/hodl/cpuminer-hodl.o' failed
make[2]: *** [algo/hodl/cpuminer-hodl.o] Error 1
make[2]: *** Waiting for unfinished jobs....
mv -f algo/hodl/.deps/cpuminer-hodl_arith_uint256.Tpo algo/hodl/.deps/cpuminer-hodl_arith_uint256.Po
mv -f algo/echo/aes_ni/.deps/cpuminer-hash.Tpo algo/echo/aes_ni/.deps/cpuminer-hash.Po
mv -f algo/haval/.deps/cpuminer-haval.Tpo algo/haval/.deps/cpuminer-haval.Po
make[2]: Leaving directory '/root/cpuminer-opt'
Makefile:3478: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/root/cpuminer-opt'
Makefile:670: recipe for target 'all' failed
make: *** [all] Error 2
strip: 'cpuminer': No such file

can anybody please help? Cry

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: bookstime6 on January 22, 2017, 07:53:41 AM

Is there a list of which of the algorithms use AVX and/or AVX2 on supported CPU's? The original post and readme say about 20 of the 40 support AVX2 but I can't find a list.

I'm mining XMR here, and I see the cryptonight algo doesn't support AVX. I assume it would be better if I mined a coin which has an algo which does take advantage of AVX instructions?

Code:

         **********  cpuminer-opt 3.5.0  *********** 
     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:        Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz
CPU features: SSE2 AES AVX
SW built on Jan 22 2017 with GCC 5.4.0
SW features: SSE2 AES AVX
Algo features: SSE2 AES
Start mining with SSE2 AES

I haven't made a list. You shouldn't choose an algo simply based on whether the algo has certain features. Choose it because
it's more profitable than other algos regardless of the features. Some algos are resistant to parallelism but it doesn't mean they
aren't as profitable as those that aren't.

Edit: Let me rewrite the last sentence from the opposite perspective. Some algos are able to use AVX but it doesn't necessarily
make them more profitable than those that are resistant.

In addition GPUs are better at parallelism so any algo that can be parallelized is dominated by GPUs or ASICs. The only real
advantage a CPU has is HW AES support. GPUs don't have it therefore any algo that uses a lot of AES has a natural advantage
on a CPU. Cryptonight is an example of an algo that uses a lot of AES.

Many newer algos have been designed to require high memory bandwidth. This creates challenges for both CPUs and GPUs
beyond their compute capability. Optimizing the compute performance won't improve the hash rate if the memory system
is already bottlenecked. That's what happened when I optimized zcoin for AVX2. Even before optimizing it maxed out with
only 3 CPU threads due to the memory load.

bookstime6

newbie

Activity: 18

Merit: 0

Is there a list of which of the algorithms use AVX and/or AVX2 on supported CPU's? The original post and readme say about 20 of the 40 support AVX2 but I can't find a list.

I'm mining XMR here, and I see the cryptonight algo doesn't support AVX. I assume it would be better if I mined a coin which has an algo which does take advantage of AVX instructions?

Code:

         **********  cpuminer-opt 3.5.0  *********** 
     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:        Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz
CPU features: SSE2 AES AVX
SW built on Jan 22 2017 with GCC 5.4.0
SW features: SSE2 AES AVX
Algo features: SSE2 AES
Start mining with SSE2 AES

m1n1ngP4d4w4n

full member

Activity: 224

Merit: 100

CryptoLearner

Quote from: joblo on January 21, 2017, 07:44:00 PM

Quote from: m1n1ngP4d4w4n on January 21, 2017, 04:23:20 PM

Quote from: joblo on January 21, 2017, 04:06:11 PM

Looks like a clear difference. They likely bought a closed source miner and tied it to their pool.

Edit: try playing with the thread count. 4 threads is usually better. The formula for the optimum thread count is
(L3 cache size / 2MB). An i7 and your xeon have 8MB L3.

Thx for the tips, i will try to see if i can do better

will report asap

A couple more observations, your xeon doesn't support AES so that will slow it down and your atom only has 4MB of cache.
Neither are good choices for mining.

Oh yes definitly they're not worth mining, but they allow me to learn, and they cost me nothing to make run (i don't pay anything for them). I was just surprised @ the difference of hashing, but you may be right it's probably a private miner (possibly to bring them botnet hashing power since it seems to be the most efficient linux based cpu miner). I tested different threads combination but it's not improving things. Less thread or more threads give about the same difference.

Quote from: joblo on January 21, 2017, 09:06:21 PM

I found a pretty good workaround for the problem of git deleting empty directories.
Any dummy file will do but I like the recommended .gitignore solution.

http://stackoverflow.com/questions/115983/how-can-i-add-an-empty-directory-to-a-git-repository.

I managed to get bastion to 185 kH/s on my i7-6700K but that is probably it.

Oh righhttt forgot about this one, ah well been a few years i used github ^^;; good you found an elegant solution Cool

joblo

legendary

Activity: 1470

Merit: 1114

I found a pretty good workaround for the problem of git deleting empty directories.
Any dummy file will do but I like the recommended .gitignore solution.

http://stackoverflow.com/questions/115983/how-can-i-add-an-empty-directory-to-a-git-repository.

I managed to get bastion to 185 kH/s on my i7-6700K but that is probably it.

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: m1n1ngP4d4w4n on January 21, 2017, 04:23:20 PM

Quote from: joblo on January 21, 2017, 04:06:11 PM

Looks like a clear difference. They likely bought a closed source miner and tied it to their pool.

Edit: try playing with the thread count. 4 threads is usually better. The formula for the optimum thread count is
(L3 cache size / 2MB). An i7 and your xeon have 8MB L3.

Thx for the tips, i will try to see if i can do better

will report asap

A couple more observations, your xeon doesn't support AES so that will slow it down and your atom only has 4MB of cache.
Neither are good choices for mining.

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: t2yax on January 21, 2017, 02:45:03 PM

you can use exchanges as a online wallet i think, so in this situation you can use bittrex joincoin wallet

It doesn't look that way to me. They give me a key that maps to an address where the mined coins go.
I need to import that key into a wallet to get access to the address and the coins in it.

If you can exlain how to do that without installing the wallet let me know.

I don't know why their messing with keys when most other no-login pools simply use the address directly.
It makes me suspicious, private keys are not meant to be exchanged.

Edit: Nevermind. Elsewhere it says it accepts an address as the user. I don't have an account at bittrex yet
but it's better than installing a wallet.

edit: First test of bastion on i7-6700K gets 184 kH/s vs 169. Will look for more.

m1n1ngP4d4w4n

full member

Activity: 224

Merit: 100

CryptoLearner

Quote from: joblo on January 21, 2017, 04:06:11 PM

Looks like a clear difference. They likely bought a closed source miner and tied it to their pool.

Edit: try playing with the thread count. 4 threads is usually better. The formula for the optimum thread count is
(L3 cache size / 2MB). An i7 and your xeon have 8MB L3.

Thx for the tips, i will try to see if i can do better

will report asap

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: m1n1ngP4d4w4n on January 21, 2017, 03:25:41 PM

Quote from: doktor83 on January 21, 2017, 06:43:46 AM

Which algo ?

Quote from: joblo on January 21, 2017, 09:28:56 AM

Quote from: doktor83 on January 21, 2017, 06:43:46 AM

Which algo ?

That was my first question. My second question is if the hashrate was from the miner or the pool. The miner
can report anything it wants.

Edit: third question, how much difference?

Here is more infos, sorry i wasn't accurate.

-= Algo =-

Cryptonight (XMR)

-= Software =-

cpuminer-opt 3.5.0 (compiled with CFLAGS="-O3 -march=native -Wall" CXXFLAGS="$CFLAGS -std=gnu++11" ./configure --with-curl)
minergate-cli 4.04

-= OS / CPU =-

CPU1
Debian x64 8.6
CPU: Intel(R) Atom(TM) CPU C2750 @ 2.40GHz
CPU features: SSE2 AES
SW built on Jan 13 2017 with GCC 4.9.2
SW features: SSE2 AES
Algo features: SSE2 AES
Start mining with SSE2 AES

CPU2
Debian x64 7.11
CPU: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz
CPU features: SSE2
SW built on Jan 21 2017 with GCC 4.7.2
SW features: SSE2
Algo features: SSE2 AES
Start mining with SSE2

-= cmdline =-

Minergate
XMR-mono : cpuminer -a cryptonight -o stratum+tcp://fcn-xmr.pool.minergate.com:45590 -u xxx -p x / minergate-cli -user xxx -xmr
XMR+FCN : cpuminer -a cryptonight -o stratum+tcp://xmr.pool.minergate.com:45560 -u xxxx -p x / minergate-cli -user xxx -fcn+xmr

Proshash
XMR-Mono : cpuminer -a cryptonight -o stratum+tcp://xmr.prohash.net:1111 -u xxx -p x

i tried both mono & dual mining, hash are near identical (more or less 0.5%)

-= Result =-

minergate-cli 4.04
reported miner hashrate : CPU1 - 67.8 H/s / CPU2 - 60.19 H/s
reported pool hashrate : CPU1 - 67.4 H/s / CPU2 - 59.88 H/s

cpuminer-opt 3.5.0
reported miner hashrate : CPU1 - 60.73 H/s / CPU2 - 55.80 H/s
reported pool (prohash) hashrate : CPU1 - 60.2 H/s / CPU2 - 55.3 H/s
reported minergate pool hashrate : CPU1 - 59.85 H/s / CPU2 - 55.1 H/s

so about 10% difference, i don't know what to think, if someone has similar experience. At first i thought minergate was favoring their own miner by showing advantageous hashrate in both the miner and the pool, but i get the same difference by using alternate miner on the minergate pool. That said with the low rates of minergate, i would probably earn more mining to another pool even with lower hashrate. But it just make me curious. They could also bullshit other alternative miners, reducing hashrate when alternative miner are used on their pool to force people using theirs, but i don't see what it would make them gain by doing that...

Looks like a clear difference. They likely bought a closed source miner and tied it to their pool.

Edit: try playing with the thread count. 4 threads is usually better. The formula for the optimum thread count is
(L3 cache size / 2MB). An i7 and your xeon have 8MB L3.

m1n1ngP4d4w4n

full member

Activity: 224

Merit: 100

CryptoLearner

Quote from: doktor83 on January 21, 2017, 06:43:46 AM

Which algo ?

Quote from: joblo on January 21, 2017, 09:28:56 AM

Quote from: doktor83 on January 21, 2017, 06:43:46 AM

Which algo ?

That was my first question. My second question is if the hashrate was from the miner or the pool. The miner
can report anything it wants.

Edit: third question, how much difference?

Here is more infos, sorry i wasn't accurate.

-= Algo =-

Cryptonight (XMR)

-= Software =-

cpuminer-opt 3.5.0 (compiled with CFLAGS="-O3 -march=native -Wall" CXXFLAGS="$CFLAGS -std=gnu++11" ./configure --with-curl)
minergate-cli 4.04

-= OS / CPU =-

CPU1
Debian x64 8.6
CPU: Intel(R) Atom(TM) CPU C2750 @ 2.40GHz
CPU features: SSE2 AES
SW built on Jan 13 2017 with GCC 4.9.2
SW features: SSE2 AES
Algo features: SSE2 AES
Start mining with SSE2 AES

CPU2
Debian x64 7.11
CPU: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz
CPU features: SSE2
SW built on Jan 21 2017 with GCC 4.7.2
SW features: SSE2
Algo features: SSE2 AES
Start mining with SSE2

-= cmdline =-

Minergate
XMR-mono : cpuminer -a cryptonight -o stratum+tcp://fcn-xmr.pool.minergate.com:45590 -u xxx -p x / minergate-cli -user xxx -xmr
XMR+FCN : cpuminer -a cryptonight -o stratum+tcp://xmr.pool.minergate.com:45560 -u xxxx -p x / minergate-cli -user xxx -fcn+xmr

Proshash
XMR-Mono : cpuminer -a cryptonight -o stratum+tcp://xmr.prohash.net:1111 -u xxx -p x

i tried both mono & dual mining, hash are near identical (more or less 0.5%)

-= Result =-

minergate-cli 4.04
reported miner hashrate : CPU1 - 67.8 H/s / CPU2 - 60.19 H/s
reported pool hashrate : CPU1 - 67.4 H/s / CPU2 - 59.88 H/s

cpuminer-opt 3.5.0
reported miner hashrate : CPU1 - 60.73 H/s / CPU2 - 55.80 H/s
reported pool (prohash) hashrate : CPU1 - 60.2 H/s / CPU2 - 55.3 H/s
reported minergate pool hashrate : CPU1 - 59.85 H/s / CPU2 - 55.1 H/s

so about 10% difference, i don't know what to think, if someone has similar experience. At first i thought minergate was favoring their own miner by showing advantageous hashrate in both the miner and the pool, but i get the same difference by using alternate miner on the minergate pool. That said with the low rates of minergate, i would probably earn more mining to another pool even with lower hashrate. But it just make me curious. They could also bullshit other alternative miners, reducing hashrate when alternative miner are used on their pool to force people using theirs, but i don't see what it would make them gain by doing that...

t2yax

sr. member

Activity: 462

Merit: 250

Arianee:Smart-link Connecting Owners,Assets,Brands

you can use exchanges as a online wallet i think, so in this situation you can use bittrex joincoin wallet

minerbaba

newbie

Activity: 91

Merit: 0

Quote from: Newton90 on January 21, 2017, 12:00:05 PM

what speed for i7/i5 haswell family?

cpuminer-opt-3.5.0-windows>cpuminer-core-avx2 -o stratum+tcp://stratum.coinspool.cu.cc:3046 -a bastion -u JfvSheuHDZ1tytaXYM9TswC5fqhRdpMbLj -p Password -t 4

********** cpuminer-opt 3.5.0 ***********
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: Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz
CPU features: SSE2 AES AVX AVX2
SW built on Jan 12 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2
Start mining with SSE2

[2017-01-22 00:06:40] Starting Stratum on stratum+tcp://stratum.coinspool.cu.cc:3046
[2017-01-22 00:06:40] 4 miner threads started, using 'bastion' algorithm.
[2017-01-22 00:06:55] CPU #3: 315.21 kH, 28.44 kH/s
[2017-01-22 00:06:56] Accepted 1/1 (100%), 315.21 kH, 28.44 kH/s
[2017-01-22 00:06:57] CPU #3: 65.01 kH, 28.38 kH/s
[2017-01-22 00:06:57] CPU #2: 378.00 kH, 28.26 kH/s
[2017-01-22 00:06:57] CPU #0: 357.67 kH, 27.36 kH/s
[2017-01-22 00:06:57] CPU #1: 365.44 kH, 27.32 kH/s
[2017-01-22 00:07:40] CPU #0: 1176.87 kH, 27.23 kH/s
[2017-01-22 00:07:41] Accepted 2/2 (100%), 1985.31 kH, 111.20 kH/s
[2017-01-22 00:07:57] CPU #1: 1639.46 kH, 27.58 kH/s
[2017-01-22 00:07:57] CPU #2: 1695.66 kH, 28.43 kH/s
[2017-01-22 00:07:57] CPU #3: 1702.97 kH, 28.41 kH/s
[2017-01-22 00:07:59] CPU #1: 54.19 kH, 28.40 kH/s
[2017-01-22 00:07:59] Accepted 3/3 (100%), 4629.69 kH, 112.47 kH/s
[2017-01-22 00:08:09] CPU #1: 288.67 kH, 27.73 kH/s
[2017-01-22 00:08:09] Accepted 4/4 (100%), 4864.17 kH, 111.81 kH/s
[2017-01-22 00:08:13] CPU #0: 894.53 kH, 27.49 kH/s
[2017-01-22 00:08:14] Accepted 5/5 (100%), 4581.83 kH, 112.06 kH/s
[2017-01-22 00:08:21] CPU #0: 225.83 kH, 27.45 kH/s
[2017-01-22 00:08:22] Accepted 6/6 (100%), 3913.13 kH, 112.03 kH/s
[2017-01-22 00:08:28] CPU #2: 899.83 kH, 28.44 kH/s
[2017-01-22 00:08:29] Accepted 7/7 (100%), 3117.30 kH, 112.03 kH/s
[2017-01-22 00:08:33] CPU #1: 676.14 kH, 27.82 kH/s
[2017-01-22 00:08:34] Accepted 8/8 (100%), 3504.77 kH, 112.12 kH/s
[2017-01-22 00:08:44] CPU #2: 435.54 kH, 28.23 kH/s
[2017-01-22 00:08:44] Accepted 9/9 (100%), 3040.49 kH, 111.92 kH/s
[2017-01-22 00:08:45] CPU #0: 654.08 kH, 27.42 kH/s
[2017-01-22 00:08:46] Accepted 10/10 (100%), 3468.74 kH, 111.89 kH/s

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: t2yax on January 21, 2017, 01:51:16 PM

Quote from: joblo on January 21, 2017, 12:38:41 PM

Quote from: t2yax on January 21, 2017, 10:03:56 AM

Quote from: joblo on January 21, 2017, 09:41:36 AM

Quote from: t2yax on January 21, 2017, 04:47:20 AM

hey joblo can you add aes and avx support to bastion algorithm or did you checked for it? i know it is not widely used but.joincoin price is little bit high.so i think its worth to try.what do you think ?

It looks doable bu there are only 3 functions that have plugin optimizations, so limited gain. Is there a pool I can test on?

yes there is http://coinspool.cu.cc/
thanks joblo

That's a weird pool. It looks like I have to install a wallet qt and import their key to get my coins. I guess it will do for
testing, I won't be mining enough to worry about.

no you dont need to install qt wallet,when you reach threshold pool will pay your earnings automatically.its like 0.001 or something.
also syncing with qt wallet is PITA,also you need to use binaries from new thread here https://bitcointalksearch.org/topic/annjoincoin-j-tor-anonymous-all-algorithm-mining-new-thread-1318397

btw did you applied optimizations how is it going ?

The instructions don't say how to withdraw coins without the wallet. How do you send coins to an address of your choice?

t2yax

sr. member

Activity: 462

Merit: 250

Arianee:Smart-link Connecting Owners,Assets,Brands

Quote from: joblo on January 21, 2017, 12:38:41 PM

Quote from: t2yax on January 21, 2017, 10:03:56 AM

Quote from: joblo on January 21, 2017, 09:41:36 AM

Quote from: t2yax on January 21, 2017, 04:47:20 AM

hey joblo can you add aes and avx support to bastion algorithm or did you checked for it? i know it is not widely used but.joincoin price is little bit high.so i think its worth to try.what do you think ?

It looks doable bu there are only 3 functions that have plugin optimizations, so limited gain. Is there a pool I can test on?

yes there is http://coinspool.cu.cc/
thanks joblo

That's a weird pool. It looks like I have to install a wallet qt and import their key to get my coins. I guess it will do for
testing, I won't be mining enough to worry about.

no you dont need to install qt wallet,when you reach threshold pool will pay your earnings automatically.its like 0.001 or something.
also syncing with qt wallet is PITA,also you need to use binaries from new thread here https://bitcointalksearch.org/topic/annjoincoin-j-tor-anonymous-all-algorithm-mining-new-thread-1318397

btw did you applied optimizations how is it going ?

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: Newton90 on January 21, 2017, 12:00:05 PM

what speed for i7/i5 haswell family?

Fast.

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: t2yax on January 21, 2017, 10:03:56 AM

Quote from: joblo on January 21, 2017, 09:41:36 AM

Quote from: t2yax on January 21, 2017, 04:47:20 AM

hey joblo can you add aes and avx support to bastion algorithm or did you checked for it? i know it is not widely used but.joincoin price is little bit high.so i think its worth to try.what do you think ?

It looks doable bu there are only 3 functions that have plugin optimizations, so limited gain. Is there a pool I can test on?

yes there is http://coinspool.cu.cc/
thanks joblo

That's a weird pool. It looks like I have to install a wallet qt and import their key to get my coins. I guess it will do for
testing, I won't be mining enough to worry about.

Newton90

sr. member

Activity: 463

Merit: 256

what speed for i7/i5 haswell family?

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