Are you sure that your wallet is not mining?
I think i see what you mean. if i close minerd it still runs at 100%, but if i delete the yenten.conf and restart the wallet then it doesn't use all that cpu. thanks.
You probably had gen=1 set in the yenten.conf. This sets the wallet to automatically start mining when you open it.
As a side note, I've found that I get nearly equal hashrates running on half of available threads as running on all of them. So you may be wasting your cpu power running at 100%. In addition, the algorithm seems to rotate between threads at regular intervals when you set it this way(so for example for a 4 thread machine set to 2 threads it will run on threads 1 and 2, then 1 and 3, then 3 and 4, etc. randomly). I'm not sure if this is unique to this algorithm or is how yescrypt also works, but it's interesting.
Yeah I did have gen=1. So was my miner going slow because of that? I've been finding a lot of blocks so maybe it didn't matter.
You're right about the threads. On my i7 it looks like it maxes out at 4 threads:
1 thread = .23 khash/s
2 thread = .23 khash/s each thread, .46 khash/s total
3 thread = .17-.19 khash/s each thread .54 khash/s total
4 thread = .14-.16 khash/s each thread .6 khash/s total
5 thread = .12 khash/s each thread .6 khash/s total
6 thread = .10-.11 khash/s each thread .6 khash/s total
So what is limiting the hashrate?
My guess is the algorithm itself. The dev appears to have designed it this way on purpose to provide limiting rewards for running many threads at once. He wants the coin to be CPU mineable on an average computer so this makes it a bit like the Magi (XMG) coin in that super powerful systems provide limiting rewards. Or it could be something completely different, I have no idea.