I'm starting to get a bit concerned about this.
If I leave classic nodes in my peer list, then it seems to slow down synchronisation, If I ban them for a week, then sync zips along.
I guess I should do a full malware scan to see if anything has got at my core installation.
I'm on McDonalds WiFi, and I know that they log web activity, presumably for marketing research, but I'm not sure how to check their investigation into the use of non-standard ports.
If I leave classic nodes in my peer list, then it seems to slow down synchronisation, If I ban them for a week, then sync zips along.
I guess I should do a full malware scan to see if anything has got at my core installation.
I'm on McDonalds WiFi, and I know that they log web activity, presumably for marketing research, but I'm not sure how to check their investigation into the use of non-standard ports.
It's just like before, though not quite as bad due to some client changes, re: block timeouts, downloading from multiple peers, etc.
It's still much faster to connect to a single 'fast' node in order to synch the blockchain, than it is to connect to multiple nodes.
For the node I have on my home internet connection, I've always just used 1 maxconnection and connect to whatever server I happen to have running bitcoind at the time.
I guess if you wanted to test speed differential, you could see what I mean, re: maxconnections=1 connect=192.254.76.218 ... that's the node I have running bitcoind at the moment, anyway..
speaking of servers, dacentec restocked a whole bunch of $20 and $25 stuff yesterday. jeje.
