-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide better feedback for syncing and operations #46
Comments
I was thinking about this too. I put this in real quick to have something, but we should improve it. The other downside is that the sync routine doesn't check the new factomd height. So after 8h, you still have 8hr worth of blocks to sync. |
We should also provide a message when the node finished syncing and enters normal operation, possibly a few status updates here and there during normal operations. The question "is my node finished syncing" pops up frequently in the #support channel |
That is a good idea yea. |
fix for this in #69 |
Just wanted to see how long it would take to sync from the open node. The status report of syncing happens every 50 blocks, but the time it takes to process a single block from the open node is between ~3 and ~10 seconds. It didn't give me the first status update until 4:30 minutes were elapsed:
I think we should make it time based rather than block based or at least caution people that it's going to take a while for the first message to show up if they're syncing from the open node.
The text was updated successfully, but these errors were encountered: