Skip to content
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

Closed
benjamincburns opened this issue Dec 19, 2017 · 1 comment
Closed
Labels
F8-enhancement 🎊 An additional feature request. P9-somedaymaybe 🌞 Issue might be worth doing eventually.

Comments

@benjamincburns
Copy link

benjamincburns commented Dec 19, 2017

Boilerplate:

I'm running:

  • Which Parity version?: 1.8.4-beta
  • Which operating system?: Linux
  • How installed?: Docker
  • Are you fully synchronized?: no
  • Did you try to restart the node?: oh god yes

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:

  1. Detected when sync slowdowns are occurring
  2. Indicated sync slowdown status in the UI
  3. Tested for known potential problems on slow sync
  4. Displayed in the UI indication of detected potential sync slowdown causes
  5. Displayed in the UI whether a detected sync slowdown cause is anomalous (example: block contains known low gas price attack)
  6. Bonus: exposed all of the above information via RPC
  7. Bonus: collected per-block sync time statistics (on an opt-in basis, please!) and made this data openly available
@NikVolf NikVolf added F8-enhancement 🎊 An additional feature request. M7-ui labels Dec 21, 2017
@5chdn 5chdn added the P9-somedaymaybe 🌞 Issue might be worth doing eventually. label Jan 2, 2018
@5chdn 5chdn added this to the 1.11 & ... milestone Jan 2, 2018
@5chdn 5chdn modified the milestones: 1.11 & ..., 1.12 & ... Jan 23, 2018
@5chdn 5chdn modified the milestones: 1.12, 1.13 & ... Mar 1, 2018
@Tbaut
Copy link
Contributor

Tbaut commented Apr 24, 2018

Moving the project to https://github.com/parity-js/shell we will not migrate lower prio issues. Please reopen it there if you really think it's needed.

@Tbaut Tbaut closed this as completed Apr 24, 2018
@5chdn 5chdn modified the milestones: 1.13, 1.11 Apr 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F8-enhancement 🎊 An additional feature request. P9-somedaymaybe 🌞 Issue might be worth doing eventually.
Projects
None yet
Development

No branches or pull requests

4 participants