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
|
|
|
It's getting late, I'll build and release it tomorrow.
It's tomorrow now
|
|
|
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 ?!
|
|
|
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
|
|
|
Something still not good, as can be seen on your capture, the hashrate keeps falling and falling...
I managed to squeeze out a little bit more speed by using the aes_ni version of groestl,setting it's datalenght to 512 instead of 1024. But still the falling hashrate ...
should be the thermal throttling maybe, but this never happens on Limx version.
|
|
|
Something still not good, as can be seen on your capture, the hashrate keeps falling and falling... I managed to squeeze out a little bit more speed by using the aes_ni version of groestl,setting it's datalenght to 512 instead of 1024. But still the falling hashrate ...
|
|
|
damn gremlins
|
|
|
yes, i only made one "compatible" binary for now... my windows build env is a bit messed up for the other ones i tested different compilers recently and the CPU #0 didnt put results in your log, 4x 66 should be 264 I compiled it myself on mingw. Yes, there should be 4 threads working, but as you can see on the pic only 3 are working. WHen i put 5 threads there are really 4 working threads etc etc. It's always t-1. Edit: Edited joblo's cpuminer opt with your optimizations and here everything works ok :
|
|
|
Threads 4 , no cpu 0 thread.. This is on windows, you are probably testing it on nix.
|
|
|
I think you have some kind of bug : i start mining with 4 threads, but always work only 3. Yeah its always threads-1 If i put 2 , then it uses 1. If i put 3, then it uses 2
|
|
|
see my git, same permut (starting with bmw 80) before : 2017-01-26 19:16:55] CPU #1: 1.26 kH/s [2017-01-26 19:16:55] CPU #2: 1.33 kH/s [2017-01-26 19:16:55] CPU #0: 1.27 kH/s [2017-01-26 19:17:28] timetravel block 387151, diff 0.419
now: [2017-01-26 19:20:33] CPU #2: 78.91 kH/s [2017-01-26 19:20:33] CPU #3: 76.86 kH/s [2017-01-26 19:20:33] CPU #1: 74.50 kH/s [2017-01-26 19:20:36] accepted: 2/2 (diff 0.007), 308.84 kH/s yes!
with a few lines changes on linux with an i5 4440 (with bmw512 as first algo) 2x bitbandi miner speed is this the timetraveler ? edit: oh yeah baby it is
|
|
|
Guys, just NAT your 4004 port and you will get more connections
|
|
|
Yes, this is it. Nice hashrate
|
|
|
just wait to find a block
|
|
|
Yeah, the hashrate on this one does not drop after some time.
|
|
|
guys think about mining this again : very hard now to find a block, and check your power consumption...
|
|
|
draws "only" double the electricity as cryptonight algo This is sick.
|
|
|
ya, it's almost 100% faster Thank you
|
|
|
|