Jonathan Moody

Another one just discovered: ``` ====================================================================== [470](https://github.com/moodyjon/lbry-sdk/actions/runs/3447738325/jobs/5754062366#step:11:471) ERROR: test_sync_with_encryption_and_password_change (integration.blockchain.test_wallet_commands.WalletEncryptionAndSynchronization) [471](https://github.com/moodyjon/lbry-sdk/actions/runs/3447738325/jobs/5754062366#step:11:472) ---------------------------------------------------------------------- [472](https://github.com/moodyjon/lbry-sdk/actions/runs/3447738325/jobs/5754062366#step:11:473) Traceback (most recent call last): [473](https://github.com/moodyjon/lbry-sdk/actions/runs/3447738325/jobs/5754062366#step:11:474) File "/home/runner/work/lbry-sdk/lbry-sdk/lbry/testcase.py", line 145, in run [474](https://github.com/moodyjon/lbry-sdk/actions/runs/3447738325/jobs/5754062366#step:11:475) self.loop.run_until_complete(maybe_coroutine) [475](https://github.com/moodyjon/lbry-sdk/actions/runs/3447738325/jobs/5754062366#step:11:476) File "/opt/hostedtoolcache/Python/3.7.15/x64/lib/python3.7/asyncio/base_events.py",...

See also #3704

You might also try to tweak some environment variables `GOGC` and `GOMEMLIMIT` to get behavior that is friendlier to your 16GB memory + 16GB swap environment. The default settings are...

I suspect at least part of the problem is lies here: https://github.com/lbryio/lbcd/blob/6b0e7592c6e136611caae04831a36db432cc1c39/rpcclient/chain.go#L488 There was a catch-all "Lbcd" version added at some point, and it doesn't count as "Post19". So "Lbcd"...

Wow. 10 minutes for claimtrie build. :-( Something's not right.... That's so bad that it makes me suspect that there was some extra load on the machine at some point....

Yes, it's showing claimtrie build time improvement (2min after, 3min before), but not overall sync time AFAICT. It takes me many days to sync from a remote node. Here is...

Regarding sha256 performance discrepancy: https://github.com/golang/go/tree/master/src/crypto/sha256 The performance you get depends on availability of special CPU instructions. go tool pprof --svg --show_from sha256 XXX.cpu Mine (arm64):  Yours (???): 

Focusing on GC scanobject: go tool pprof --svg --show_from scanobject XXX.cpu Mine (arm64):  Yours (???):  I don't see anything obviously architecture-specific. But yours is registering a lot more...

Demote to draft status as this is a sensitive code area. There is an outstanding bug being investigated at this time: https://github.com/lbryio/lbcd/issues/71

I tracked several of these down, and the cause is the mixing of lbrycrd and lbcd. You can find these new messages in the code of lbcd and lbcwallet. @roylee17...