Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 111. (Read 444067 times)
January 27, 2017, 03:44:26 PM
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)
January 27, 2017, 03:35:51 PM
cpuminer-opt v3.5.2 with support for Timetravel algo (Machinecoin), optimized then optimized some more.
https://bitcointalksearch.org/topic/m.13542056
https://bitcointalksearch.org/topic/m.13542056
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?
January 27, 2017, 03:20:52 PM
cpuminer-opt v3.5.2 with support for Timetravel algo (Machinecoin), optimized then optimized some more.
https://bitcointalksearch.org/topic/m.13542056
https://bitcointalksearch.org/topic/m.13542056
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.
January 27, 2017, 02:59:14 PM
cpuminer-opt v3.5.2 with support for Timetravel algo (Machinecoin), optimized then optimized some more.
https://bitcointalksearch.org/topic/m.13542056
https://bitcointalksearch.org/topic/m.13542056
congrats, x2 on my Xeon E5v4
http://yiimp.ccminer.org/bench?chip=27&algo=timetravel
January 27, 2017, 01:29:40 PM
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.
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.
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.
Thanks for your answer.
January 27, 2017, 01:11:44 PM
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.
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
January 27, 2017, 12:57:35 PM
cpuminer-opt v3.5.2 with support for Timetravel algo (Machinecoin), optimized then optimized some more.
https://bitcointalksearch.org/topic/m.13542056
https://bitcointalksearch.org/topic/m.13542056
January 27, 2017, 12:41:21 PM
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.
January 27, 2017, 12:32:29 PM
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.
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.
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.
January 27, 2017, 11:42:07 AM
It's getting late, I'll build and release it tomorrow.
It's tomorrow now
January 27, 2017, 11:37:35 AM
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.
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.
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 ?!
January 27, 2017, 11:27:56 AM
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.
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.
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.
? ? ?
January 27, 2017, 10:40:50 AM
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.
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.
January 27, 2017, 08:57:27 AM
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.
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.
January 27, 2017, 12:34:43 AM
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
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
January 26, 2017, 11:08:29 PM
I think I'm pretty much settled on the final implementation of Timetravel.
Final hashrate on i7-4790K 4 GHz is right around 800 kH/s
In addition to backing out SSE2 Luffa I had to back out the optomized ctx init for Groestl.
Something weird there, it works fine for a while then segfaults.
I also moved the permutation calculation to scanhash and and back to per-thread. I didn't see any performance
difference and I think the global array updated by stratum thread introduced a race condition with the miner
threads restarting resulting in occasional invalid job id rejects.
It's getting late, I'll build and release it tomorrow.
Final hashrate on i7-4790K 4 GHz is right around 800 kH/s
In addition to backing out SSE2 Luffa I had to back out the optomized ctx init for Groestl.
Something weird there, it works fine for a while then segfaults.
I also moved the permutation calculation to scanhash and and back to per-thread. I didn't see any performance
difference and I think the global array updated by stratum thread introduced a race condition with the miner
threads restarting resulting in occasional invalid job id rejects.
It's getting late, I'll build and release it tomorrow.
January 26, 2017, 08:34:04 PM
Luffa strikes again. The SSE2 optimized Luffa function stopped working on timetravel.
Everything was hashing fine and then the hashrate jumped and it stopped submitting shares.
There was not a new block or any other apparent trigger.
Restarting the miner doesn't work, only restoring the sph version of Luffa fixes it.
Similar problem occurs with SSE2 Luffa on Qubit and Xevan with no shares ever submitted.
New symptom this time, started fine then broke, could be a clue.
Everything was hashing fine and then the hashrate jumped and it stopped submitting shares.
There was not a new block or any other apparent trigger.
Restarting the miner doesn't work, only restoring the sph version of Luffa fixes it.
Similar problem occurs with SSE2 Luffa on Qubit and Xevan with no shares ever submitted.
New symptom this time, started fine then broke, could be a clue.
Code:
[2017-01-26 19:16:44] Accepted 164/168 (97.6%), 11.22 MH, 735.62 kH/s, 64C
[2017-01-26 19:16:58] CPU #0: 2706.77 kH, 93.75 kH/s
[2017-01-26 19:16:58] Accepted 165/169 (97.6%), 9757.02 kH, 737.19 kH/s, 62C
[2017-01-26 19:17:05] CPU #0: 739.42 kH, 93.66 kH/s
[2017-01-26 19:17:06] Accepted 166/170 (97.6%), 7789.67 kH, 737.10 kH/s, 64C
[2017-01-26 19:17:15] CPU #3: 4284.87 kH, 93.26 kH/s
[2017-01-26 19:17:15] Accepted 167/171 (97.7%), 11.77 MH, 737.15 kH/s, 63C
[2017-01-26 19:17:24] CPU #6: 5160.18 kH, 93.90 kH/s
[2017-01-26 19:17:28] CPU #1: 5549.19 kH, 93.46 kH/s
[2017-01-26 19:17:29] CPU #7: 5593.32 kH, 93.31 kH/s
[2017-01-26 19:17:29] CPU #5: 5627.40 kH, 93.63 kH/s
[2017-01-26 19:17:30] CPU #2: 5459.40 kH, 88.97 kH/s
[2017-01-26 19:17:32] CPU #0: 2472.36 kH, 93.77 kH/s
[2017-01-26 19:17:32] CPU #4: 4450.00 kH, 93.57 kH/s
[2017-01-26 19:17:32] CPU #7: 297.38 kH, 93.34 kH/s
[2017-01-26 19:17:32] CPU #2: 160.54 kH, 90.58 kH/s
[2017-01-26 19:17:32] CPU #6: 767.45 kH, 93.86 kH/s
[2017-01-26 19:17:32] CPU #3: 1603.72 kH, 93.30 kH/s
[2017-01-26 19:17:32] CPU #1: 351.17 kH, 93.50 kH/s
[2017-01-26 19:17:32] CPU #5: 283.92 kH, 93.69 kH/s
[2017-01-26 19:18:27] CPU #4: 5614.12 kH, 101.83 kH/s <---- hashrate increased, no shares submitted after this even after new block
[2017-01-26 19:18:27] CPU #7: 5600.27 kH, 101.06 kH/s
[2017-01-26 19:18:27] CPU #1: 5610.26 kH, 101.19 kH/s
[2017-01-26 19:18:27] CPU #0: 5626.28 kH, 101.41 kH/s
[2017-01-26 19:18:27] CPU #6: 5631.70 kH, 101.38 kH/s
[2017-01-26 19:18:27] CPU #3: 5598.09 kH, 100.66 kH/s
[2017-01-26 19:18:28] CPU #5: 5621.38 kH, 100.83 kH/s
[2017-01-26 19:18:28] CPU #2: 5434.56 kH, 97.30 kH/s
[2017-01-26 19:18:35] CPU #4: 814.54 kH, 101.83 kH/s
[2017-01-26 19:18:35] CPU #6: 765.25 kH, 100.96 kH/s
[2017-01-26 19:18:35] CPU #5: 743.28 kH, 100.71 kH/s
[2017-01-26 19:18:35] CPU #1: 778.84 kH, 101.30 kH/s
[2017-01-26 19:18:35] CPU #2: 732.46 kH, 100.64 kH/s
[2017-01-26 19:18:35] CPU #7: 783.21 kH, 101.50 kH/s
[2017-01-26 19:18:35] CPU #0: 775.59 kH, 101.41 kH/s
January 26, 2017, 08:23:47 PM
ah ok, well, forum binaries without sources are not in my time log :p
January 26, 2017, 07:06:20 PM
January 26, 2017, 06:52:27 PM
what is limx ?
Jump to: