10:05:38 <ErCiccione[m]> Could be of interest here: https://twitter.com/lopp/status/1224097293038751749
10:06:07 <ErCiccione[m]> for non-twiter folks: "Full validation sync of monero 0.15.0.1 to block 2025045 on my benchmark machine took 1 day 2 hours 40 min. Caching policy is effective; only read 9GB from disk while writing 297GB. Bottleneck appears to be software rather than hardware."
10:06:15 <ErCiccione[m]> from Jameson Lopp
10:10:56 <sech1> Well, full validation sync is slow
10:11:50 <sech1> It takes at least 12 hours on a modern CPU to verify all PoW hashes from 2+ million blocks
10:18:01 <ErCiccione[m]> Yeah, what hits is the huge difference with a bitcoin core node 0.15.1 (i know our tx are way bigger and our times are slower for a reason), which he synced in 162 min last year. assuming he used the same machine for both.
10:19:38 <sech1> Cryptonight hash verification takes 20 ms on an unoptimized PC (I doubt he configured large pages properly). Now compare it with Bitcoin's SHA256.
10:38:35 <smooth> 12 hours is assuming one core, which is unlikely for most modern PCs
10:45:41 <M5M400> took about 3h on my ryzen laptop. btw the "trusted daemon" checkbox in gui should prevent verifications, right? seems it doesn't work in gui 0.15.0.2
10:51:30 <selsta> prevent verifications?
10:54:18 <selsta> there were problems with the checkbox in the past but not in v0.15.0.2
13:12:11 <Inge-> how well does monerod node sync utilize multiple cores?
13:27:53 <moneromooo> 1 day isn't bad for full verification. Does he mention how much it took before ? I know he did that experiment before, and historical sync got sped up since.
13:37:04 <smooth> Inge-: It seems to use the first few reasonably well, after that it might not be that great
13:37:34 <smooth> Possibly some tuning would help, did not ever try
13:40:05 <moneromooo> It depends what it's verifying. IIRC PoW uses everything. Other things vary. It *could* preverify PoW so there's always some PoW ready for starved CPUs.
16:36:12 <hyc> M5M400: the trusted daemon option for wallets only means the wallet will do some RPCs that it otherwise would avoid
16:37:00 <hyc> and yes, currently monerod will use all available cores
16:38:03 <hyc> whether that's a good idea or not is debatable. Intel CPUs are cache-starved, so it's better to use fewer threads than cores.
16:38:27 <hyc> AMD tends to be fine with threads == cores
19:23:59 <Insight> is it technically possible to run a gui wallet on a private testnet?
19:24:44 <moneromooo> Yes.
21:23:20 <cohcho> Is it possible to be notified when core isn't busy without polling or patch that triggers --block-notify within cryptonote::core::on_synchronized() ?
21:27:20 <asymptotically> cohcho: i was just wondering the same thing today :)
21:28:45 <cohcho> I need it because of my hardware may freeze unexpectedly and i'll need to resart monerod and pool as soon as possible
21:46:26 <asymptotically> cohcho: maybe we could add a new flag, like --delay-block-notifications