-
DataHoarder
shouldn't take more than 5-10 minutes or so even if clean
-
DataHoarder
maybe it hits the limit of how long you can be desync'd and get dropped from peers
-
DataHoarder
backup the peer list and fully remove it, let it rebuild it
-
hyc
dunno. it's been doing add_block: xxx" the whole time
-
DataHoarder
cache is also only saved up after a full resync
-
DataHoarder
what are you up to?
-
hyc
working down to mainchain 3030856
-
hyc
3031154
-
hyc
side height 6279370
-
DataHoarder
that's about 9 hours ago
-
DataHoarder
3h more to go :D
-
hyc
ugh
-
DataHoarder
-
hyc
how far back is it going to go? 12 hours?
-
DataHoarder
about so, two PPLNS windows + slightly extra
-
DataHoarder
I should maybe make a "download compressed cache" feature on observer :D
-
hyc
heh
-
DataHoarder
client will still verify blocks there
-
hyc
well, 12 hours back should overlap with when it was last online
-
DataHoarder
-
DataHoarder
also it's mini, which has larger blocks
-
DataHoarder
many miner outputs, specially in first download
-
hyc
ah, done.
-
hyc
sheesh
-
hyc
just over an hour
-
m-relay
<ofrnxmr:monero.social> how is it if using --nocache ?
-
m-relay
<ofrnxmr:monero.social> (im probably misremembering the flag)
-
DataHoarder
probably about the same time as they had to download all the new blocks
-
DataHoarder
it just doesn't lookup the cache at all (or saves them
-
m-relay
<ofrnxmr:monero.social> Maybe just bad peers / slow download? 45mins sounds long
-
m-relay
<ofrnxmr:monero.social> Sounds like 40mins longer than id think sounded normal (acceptable?)
-
DataHoarder
5Mbits and will get bad peers probably that way
-
DataHoarder
it's somewhat latency sensitive for roundtrips too
-
DataHoarder
afaik latest changes should have improved that
-
m-relay
<ofrnxmr:monero.social> Ah, 5mbit not mb
-
sech1
hyc maybe you caught some very slow peer who also didn't tell you about other peers... You need to check who you're connected to using "peers" command
-
sech1
or are you syncing it on a potato SBC?
-
sech1
immediate restart should sync fast because it will just load everything from the cache
-
hyc
syncing it on an rk3588 with 32GB RAM, it's a fairly decent mini pc
-
sech1
if restart with cache enabled is still very slow, I'd like to see log level 6 log of that
-
hyc
ok I'll try restarting it now
-
sech1
rk3588 has aes, right?
-
hyc
yep
-
hyc
seems to be going a lot faster now. it's with no-randomx, so keeping monerod 100% busy
-
hyc
and I see a lot of "using cached block" msgs flying by
-
hyc
done
-
hyc
about 5 minutes, yeah
-
sech1
so it was probably a slow peer. P2Pool tries to choose a peer with the lowest ping, but if this peer turns out to be slow, it's just a bad luck
-
hyc
ok. never happened before
-
sech1
I actually run p2pool without the cache, and it always restarts quickly
-
sech1
so never happened to me too
-
hyc
as a matter of fact, I remember seeing a message about too slow ping time on that startup
-
hyc
I assumed it was complaining just because the 4G connection has generally slow pings\
-
QuickBASIC
5Mbit on 4G? You live in the boonies hyc?
-
hyc
yep
-
QuickBASIC
I lived in bumfuck Bavaria for a year and had miserable speeds on mobile and cable and swore to never live in rural Europe ever again lol.
-
hyc
the gigabit fiber has been working fine for like 2 years.
-
hyc
only died on me once before, when someone ran their digger thru the line
-
QuickBASIC
I wish. Fiber is so sparse in America. Cable isn't bad though I get 250 down 50 up.
-
QuickBASIC
"Business class" b/c wifey and I work remote.
-
sech1
hyc running with --no-randomx also adds your node ping time to each block's sync time. So if it complained about "too slow ping", it could've been your node
-
m-relay
<chch3003:monero.social> Hello! Trying to mine on my Macbook M1 Max with P2pool Mini from official GUI but it crashes directly with "Timed out, local node is not responding after 120 seconds. Please check your wallet and daemon log for errors. You can also try to start monerod manually. Exiting p2pool. Please check that port 18083 is available." Any idea what I can do?
-
sech1
It's something with your Monero node. It's better to ask in #monero-gui