< 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
< dfmb__> thois
< 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
< 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
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/376294cde6b1...88d8b4e182bf
< bitcoin-git> bitcoin/master 420fa07 Harris: fuzz: use std::optional for sep_pos variable
< bitcoin-git> bitcoin/master 88d8b4e MarcoFalke: Merge #18901: fuzz: use std::optional for sep_pos_opt variable
< 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
< 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
< 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
< 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
< 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
< Dizzle> in the SHA-NI implementation on AMD chips, is it normal for the CPU to appear underutilized during blockchain sync?
< phantomcircuit> Dizzle, initial sync or a reindex?
< Dizzle> phantomcircuit: initial sync. Seeing a single CPU core bursting to 100%, but usually around 12%. TCP recv queues from peers are large
< phantomcircuit> Dizzle, hdd or ssd?
< Dizzle> SATA HDD
< sipa> how high is dbcache setting?
< Dizzle> Probably at the default. In debug log, cache= gets up to around 600MiB
< sipa> your node is spending most of its time doing database I/o
< sipa> increasing dbcache will reduce that
< Dizzle> Thanks, sipa. I guess I was spoiled on SSD runs and disk i/o didn't occur to me