02:09 < luke-jr> [23:47:07] <sipa> MarcoFalke: i don't think issues should be closed because nobody is working on them <-- indeed, some look like "good first issue" material

07:42 < dfmb__> thois

10:17 < bitcoin-git> [bitcoin] practicalswift opened pull request #18920: doc: Document how to analyze Bitcoin Core using clang-tidy (master...static-analysis-clang-tidy) https://github.com/bitcoin/bitcoin/pull/18920

11:28 < bitcoin-git> [bitcoin] fanquake opened pull request #18921: build: add stack-clash and control-flow protection options to hardening flags (master...add_cfi_to_hardening) https://github.com/bitcoin/bitcoin/pull/18921

11:32 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/376294cde6b1...88d8b4e182bf

11:32 < bitcoin-git> bitcoin/master 420fa07 Harris: fuzz: use std::optional for sep_pos variable

11:32 < bitcoin-git> bitcoin/master 88d8b4e MarcoFalke: Merge #18901: fuzz: use std::optional for sep_pos_opt variable

11:32 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #18901: fuzz: use std::optional for sep_pos_opt variable (master...warning-in-fuzz-tests) https://github.com/bitcoin/bitcoin/pull/18901

12:43 < bitcoin-git> [bitcoin] hebasto opened pull request #18922: gui: Do not translate InitWarning messages in debug.log (master...200509-initwarn) https://github.com/bitcoin/bitcoin/pull/18922

13:12 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #18923: wallet: Never schedule MaybeCompactWalletDB when -flushwallet is off (master...2005-walletNoFlush) https://github.com/bitcoin/bitcoin/pull/18923

19:10 < bitcoin-git> [bitcoin] naumenkogs opened pull request #18925: Add extra thread for scheduler, move TorControl and OpenAddedConnections to scheduler (master...2020_05_extra_scheduler_thread) https://github.com/bitcoin/bitcoin/pull/18925

22:39 < bitcoin-git> [bitcoin] glowang opened pull request #18926: Pass ArgsManager into functions that register args with AddArg (master...replace_global_gArgs_with_local_argsman) https://github.com/bitcoin/bitcoin/pull/18926

22:59 < Dizzle> in the SHA-NI implementation on AMD chips, is it normal for the CPU to appear underutilized during blockchain sync?

23:03 < phantomcircuit> Dizzle, initial sync or a reindex?

23:08 < Dizzle> phantomcircuit: initial sync. Seeing a single CPU core bursting to 100%, but usually around 12%. TCP recv queues from peers are large

23:08 < phantomcircuit> Dizzle, hdd or ssd?

23:09 < Dizzle> SATA HDD

23:10 < sipa> how high is dbcache setting?

23:11 < Dizzle> Probably at the default. In debug log, cache= gets up to around 600MiB

23:12 < sipa> your node is spending most of its time doing database I/o

23:12 < sipa> increasing dbcache will reduce that

23:13 < Dizzle> Thanks, sipa. I guess I was spoiled on SSD runs and disk i/o didn't occur to me