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

Improve the stability of block time #1032

Closed
i359 opened this issue Aug 15, 2019 · 7 comments
Closed

Improve the stability of block time #1032

i359 opened this issue Aug 15, 2019 · 7 comments

Comments

@i359
Copy link

i359 commented Aug 15, 2019

What causes the unstable block time, the network delay of part nodes or other ?

123

@igormcoelho
Copy link
Contributor

igormcoelho commented Aug 16, 2019

Which instability... you mean 20, 21, 23 secs ?

This have improved a lot already hahaha looks stable to me 😂

But really, there's a solution for this, in my opinion, but this requires changing CurrentBlockTime to PrevBlockTime (I opened an issue for it). Without that, its nearly impossible to get zero delay here.

Regarding tx count differences, I guess it may have been solved already on base dev code, looks like some existing p2p and TaskManager issues.

@lock9
Copy link
Contributor

lock9 commented Aug 16, 2019

🤔
@igormcoelho But this would be just a visual change right? Or do you think the displayed time is incorrect?

@igormcoelho
Copy link
Contributor

Nope, I mean, to actually finish blocks in time (or nearly close to time).

@i359
Copy link
Author

i359 commented Aug 16, 2019

Maybe further improvements are needed, thanks!

111

@igormcoelho
Copy link
Contributor

I think these 39 and 42 seconds may involve changeviews... only looking at node logs (or p2p logs) to be sure.

@lock9
Copy link
Contributor

lock9 commented Aug 20, 2019

Hi @i359, as I mentioned in the other issue, I didn't find evidence that this problem is really happening. Not sure if it was caused by some network problem but in any case, if you think this is really happening, feel free to create a new issue or request someone from the team to reopen it.
Thanks

@lock9 lock9 closed this as completed Aug 20, 2019
@vncoelho
Copy link
Member

@i359, several minor commits were made from v2.10.2 to 2.10.3, check it out. I believe nodes stability may improve.

Thanks for reporting and discussing. The topic may still need further adjustment which we are investigating closely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants