Quote from: noise23 on July 29, 2017, 07:24:20 PM

Quote from: UpUrs on July 29, 2017, 06:33:09 PM

Quote from: bitmaster1x on July 27, 2017, 08:48:34 PM

@Noise. Any plans for the rest of this and next year for TRK?

Would be great if you plan on a maintanace release to fix the high cpu load.
Maybe you can use the code from Hyperstake ?
Also there seems to be a connection bug, I only get 12 connections max. all outgoing.
Changing ports does not have any effect.
(WinXP)

There is no connection bug, 12 connections are more than enough, why would you need more?

Regarding CPU load, if you have a lot of small blocks staking then load will be high, use splitthreshold to prevent splitting into too small chunks.
Hyperstake was originally forked from TRK so the code is mostly the same.

Hyperstake (and others...) has a different way of calculating hash, calculate once and use many times, old qt code just keeps re-hashing the same thing.
Cpu load on my box is about 50% for Truck while Hyp runs mostly idle, and then my Hyp wallet has a lot more stacks then Truck wallet.
I do make use of splitthreshold (set to 2200) since my wallet is too big for manually daily re-combining so not much help for big wallets.

If connection limits of max 12 outgoing and no incoming are per design then you are right, it's no bug.
It's not a big issue since wallet works but would be better for network to have more connects out and most important also incomming.
Except for Truck all wallets that I run are maxed out, well over 50 to 100+ connects, most of them incomming.