This repository was archived by the owner on Nov 6, 2020. It is now read-only.
Add UI to educate users on potential reasons for sync slowdowns #7328
Labels
F8-enhancement 🎊
An additional feature request.
P9-somedaymaybe 🌞
Issue might be worth doing eventually.
Milestone
Boilerplate:
Description:
As a user experiencing a slowdown during a node sync, all I know is that the current "Best Block" isn't increasing, or at least that it isn't increasing as quickly as it might've been a few minutes ago. Given the time involved for a full archive sync, having to figure out whether action is required when slowdowns occur, let alone which action is required, makes the initial sync feel much more high-effort and risky than it needs to be.
Sync slowdowns could be due to any of the following (and more):
It'd save new users and Parity project members lots of time if Parity:
The text was updated successfully, but these errors were encountered: