Anyone else notice that Daedalus 4.0.4 sync was immeasurably faster than 4.0.5? Anyone know why and what to do about it?
On a few machines I installed a fresh copy of 4.0.4 and it was good to go in about an hour on gigabit hardwired. Laptop took somewhat longer over 5G but that is to be expected of wireless. Updating from 4.0.4 to 4.0.5 was fine but sync on even a few days of datas seemed about as long as the initial which baffled me.
Out of curiosity I did a fresh install of 4.0.5 and fired it up. That was yesterday. The same gigabit connection it took over 20 hours to sync! When I monitored network traffic earlier today with nothing else running I was seeing over 80% CPU and memory utilization but only about 300 kpbs down?!?!? That is ludicrous as I have seen PoW miners use less resources in the distant past. This is a wallet!
When I tried importing topology from known relay nodes for my region Daedalus node crashed. When I tried increasing the valency on the relays-new.XXX default the node failed to connect and was unresponsive. Everything else I tried just made it more unstable.
I was about to try a fresh install and disabling all the tracing in the config to maybe reduce I/O but that is a shot in the dark. Apparently there are not any performance considerations at this stage and that would be fine if it would not ostracize new users. Can you imagine being in a more rural area and having to wait weeks to use an application after installing and launching it?
Has anyone successfully optimized Daedalus to connect to reliable edge relay nodes for a geographic region and/or could point me to documentation of how to do so?