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

[doktor83]

limx version is about as fast as yours Epsylon3
I'm waiting for the sources joblo, interested in what you did there.

I managed to get a little bit more hs (255hs vs 280hs), but an interesting thing happens :
its all working well and after some time the cmd window dissapers but continues to work in background LOL
I can confirm it's working because i can see its hashes on the pool side LOL

[ZenFr]

I use since several month this good miner :-), great job Joblo.

I use it with 5 differents CPUs and only with XZC (ZCoin) algorythm.

Some time, I have 2 kinds of problem : "stratum connection failed" or stratum "subscribe time out" (this is probably the same issue).
The problem can be during half an hour or more (2 or 3 hours ?), after the connection work fine again, alone, whithout intervention from me.
I have trying 3 differents pools and that is the same thing for the 3 : I don't think that is a pool problem...

Have you some advice for me ? A fix for the miner soft ?
Any body else have the same issues ?

Other question : have you any plan to increase the hashrate of this CPU miner for the ZCoin algorythm ?

Thank you.
  

[joblo]

I use since several month this good miner :-), great job Joblo.

I use it with 5 differents CPUs and only with XZC (ZCoin) algorythm.

Some time, I have 2 kinds of problem : "stratum connection failed" or stratum "subscribe time out" (this is probably the same issue).
The problem can be during half an hour or more (2 or 3 hours ?), after the connection work fine again, alone, whithout intervention from me.
I have trying 3 differents pools and that is the same thing for the 3 : I don't think that is a pool problem...

Have you some advice for me ? A fix for the miner soft ?
Any body else have the same issues ?

Other question : have you any plan to increase the hashrate of this CPU miner for the ZCoin algorythm ?

Thank you.
  

Looks like a networking issue. Use a wired connection if possible.

The current zcoin algo is bottlenecked by memory access. No amount of optimizing the code will solve that.

[ZenFr]

I use since several month this good miner :-), great job Joblo.

I use it with 5 differents CPUs and only with XZC (ZCoin) algorythm.

Some time, I have 2 kinds of problem : "stratum connection failed" or stratum "subscribe time out" (this is probably the same issue).
The problem can be during half an hour or more (2 or 3 hours ?), after the connection work fine again, alone, whithout intervention from me.
I have trying 3 differents pools and that is the same thing for the 3 : I don't think that is a pool problem...

Have you some advice for me ? A fix for the miner soft ?
Any body else have the same issues ?

Other question : have you any plan to increase the hashrate of this CPU miner for the ZCoin algorythm ?

Thank you.
  

Looks like a networking issue. Use a wired connection if possible.

The current zcoin algo is bottlenecked by memory access. No amount of optimizing the code will solve that.

Thank you for the reply.

I'm using wired connection (RJ45) for all these computers :-).
2 of these computers have GPUs and are mining other cryptos without connection problems (GPU mining works fine, just the CPU mining have issues) and the 3 other computers are specific minig ZCoin.
? ? ?

[doktor83]

I use since several month this good miner :-), great job Joblo.

I use it with 5 differents CPUs and only with XZC (ZCoin) algorythm.

Some time, I have 2 kinds of problem : "stratum connection failed" or stratum "subscribe time out" (this is probably the same issue).
The problem can be during half an hour or more (2 or 3 hours ?), after the connection work fine again, alone, whithout intervention from me.
I have trying 3 differents pools and that is the same thing for the 3 : I don't think that is a pool problem...

Have you some advice for me ? A fix for the miner soft ?
Any body else have the same issues ?

Other question : have you any plan to increase the hashrate of this CPU miner for the ZCoin algorythm ?

Thank you.
  

Looks like a networking issue. Use a wired connection if possible.

The current zcoin algo is bottlenecked by memory access. No amount of optimizing the code will solve that.

Thank you for the reply.

I'm using wired connection (RJ45) for all these computers :-).
2 of these computers have GPUs and are mining other cryptos without connection problems (GPU mining works fine, just the CPU mining have issues) and the 3 other computers are specific minig ZCoin.
? ? ?

i get a TON of stratum connection problems, so i would say it's kinda normal ?!

[doktor83]

It's getting late, I'll build and release it tomorrow.

It's tomorrow now 

[joblo]

I use since several month this good miner :-), great job Joblo.

I use it with 5 differents CPUs and only with XZC (ZCoin) algorythm.

Some time, I have 2 kinds of problem : "stratum connection failed" or stratum "subscribe time out" (this is probably the same issue).
The problem can be during half an hour or more (2 or 3 hours ?), after the connection work fine again, alone, whithout intervention from me.
I have trying 3 differents pools and that is the same thing for the 3 : I don't think that is a pool problem...

Have you some advice for me ? A fix for the miner soft ?
Any body else have the same issues ?

Other question : have you any plan to increase the hashrate of this CPU miner for the ZCoin algorythm ?

Thank you.
  

Looks like a networking issue. Use a wired connection if possible.

The current zcoin algo is bottlenecked by memory access. No amount of optimizing the code will solve that.

Thank you for the reply.

I'm using wired connection (RJ45) for all these computers :-).
2 of these computers have GPUs and are mining other cryptos without connection problems (GPU mining works fine, just the CPU mining have issues) and the 3 other computers are specific minig ZCoin.
? ? ?

i get a TON of stratum connection problems, so i would say it's kinda normal ?!

zcoin only? Many pools have problems with zcoin (incorrect hashrate etc) due to the extremely low hashrate.
If it only happens on zcoin consider it a coin problem. The stratum code in cpuminer is identical for all algos.

[joblo]

It's getting late, I'll build and release it tomorrow.

It's tomorrow now  

Git updated, formal annoucement soon.

Edit: If I messed anything up I'm blaming you, you made me rush.

[joblo]

cpuminer-opt v3.5.2 with support for Timetravel algo (Machinecoin), optimized then optimized some more.

https://bitcointalk.org/index.php?topic=1326803.msg13542056#msg13542056

[doktor83]

zcoin only? Many pools have problems with zcoin (incorrect hashrate etc) due to the extremely low hashrate.
If it only happens on zcoin consider it a coin problem. The stratum code in cpuminer is identical for all algos.

Yes, zcoin only.
Thanks for rushing

[ZenFr]

I use since several month this good miner :-), great job Joblo.

I use it with 5 differents CPUs and only with XZC (ZCoin) algorythm.

Some time, I have 2 kinds of problem : "stratum connection failed" or stratum "subscribe time out" (this is probably the same issue).
The problem can be during half an hour or more (2 or 3 hours ?), after the connection work fine again, alone, whithout intervention from me.
I have trying 3 differents pools and that is the same thing for the 3 : I don't think that is a pool problem...

Have you some advice for me ? A fix for the miner soft ?
Any body else have the same issues ?

Other question : have you any plan to increase the hashrate of this CPU miner for the ZCoin algorythm ?

Thank you.
  

Looks like a networking issue. Use a wired connection if possible.

The current zcoin algo is bottlenecked by memory access. No amount of optimizing the code will solve that.

Thank you for the reply.

I'm using wired connection (RJ45) for all these computers :-).
2 of these computers have GPUs and are mining other cryptos without connection problems (GPU mining works fine, just the CPU mining have issues) and the 3 other computers are specific minig ZCoin.
? ? ?

i get a TON of stratum connection problems, so i would say it's kinda normal ?!

zcoin only? Many pools have problems with zcoin (incorrect hashrate etc) due to the extremely low hashrate.
If it only happens on zcoin consider it a coin problem. The stratum code in cpuminer is identical for all algos.

I think ZCoin only, yes.
Thanks for your answer.

[Epsylon3]

cpuminer-opt v3.5.2 with support for Timetravel algo (Machinecoin), optimized then optimized some more.

https://bitcointalk.org/index.php?topic=1326803.msg13542056#msg13542056

congrats, x2 on my Xeon E5v4

http://yiimp.ccminer.org/bench?chip=27&algo=timetravel

[joblo]

cpuminer-opt v3.5.2 with support for Timetravel algo (Machinecoin), optimized then optimized some more.

https://bitcointalk.org/index.php?topic=1326803.msg13542056#msg13542056

congrats, x2 on my Xeon E5v4

http://yiimp.ccminer.org/bench?chip=27&algo=timetravel

Thanks for your work, I don't know how it would have taken me to find that CPU hog. It was obvious once you
pointed it out.

[thefix]

cpuminer-opt v3.5.2 with support for Timetravel algo (Machinecoin), optimized then optimized some more.

https://bitcointalk.org/index.php?topic=1326803.msg13542056#msg13542056

congrats, x2 on my Xeon E5v4

http://yiimp.ccminer.org/bench?chip=27&algo=timetravel

Just out of curiosity is your Xeon E5 setup with a quad channel memory configuration?


If you have time would you mind testing Zcoin speeds with it?

[Epsylon3]

0.1 ZCrap per day from my last test, this coin is dead for me (and not for the reward, for the whole algo mess)

[thefix]

0.1 ZCrap per day from my last test, this coin is dead for me (and not for the reward, for the whole algo mess)

I cant blame you for not being a fan of the coin as it is plagued by multiple issues at the moment.

I was just curious about the mining speeds with a quad channel setup more than anything.

I am guessing you are doing about 25 h/s with your setup

[joblo]

I think I've found the problem with the SSE2 version of Luffa. It simply doesn't support 80 byte
input. The datalen arg is ignored and it always hashes just 64 bytes. This explains why it worked for
a while in Timetravel. It also explains why it never worked in Qubit even though I passed the correct
datalen.

It looks fairly straighforward to change based on how other functions do it.

I've also been looking at the AES Groestl function. It has a lot of code that isn't used, much of it to support
odd hash lengths. Since only two hash lengths are ever used, 64 and 80 bytes, Some cleanup might give
a little boost in speed.

[Newton90]

Make sure your memory is installed correctly for 2 channel operation.

is memory mode has such influance on hashing speed?have one channel conf.

[joblo]

Make sure your memory is installed correctly for 2 channel operation.

is memory mode has such influance on hashing speed?have one channel conf.

It depend on the algo. Memory hard algos are most affected.

[joblo]

The optimized Luffa is now working for various data lengths where previously it only worked with 64 byte length.
It also now works with 512 or 1024 bit hash length.

I now have timetravel, xevan and qubit working with the optimized Luffa. This marks a significant milestone.
Except for the hard coded macros, all of the original optimized x11 functions have now been implemented in
all algos that use them.

There is still some cleanup and testing to do before release.