Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Parity using 22% CPU continuously after warp sync #2941

Closed
gavofyork opened this issue Oct 28, 2016 · 4 comments
Closed

Parity using 22% CPU continuously after warp sync #2941

gavofyork opened this issue Oct 28, 2016 · 4 comments
Assignees
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust.
Milestone

Comments

@gavofyork
Copy link
Contributor

No description provided.

@gavofyork gavofyork added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. labels Oct 28, 2016
@gavofyork gavofyork added this to the 1.4 Civility milestone Oct 28, 2016
@rphmeier
Copy link
Contributor

This seems about right. It still has to download (and now verify) ancient blocks which are being imported. Finishing the snapshot restoration isn't quite like finishing a full sync as there's still lots of work to do.

@rphmeier rphmeier changed the title Parity using 22% CPU continuously after wrap sync Parity using 22% CPU continuously after warp sync Oct 28, 2016
@arkpar
Copy link
Collaborator

arkpar commented Oct 29, 2016

Caused by tokio-rs/mio#483 mostly

@arkpar arkpar self-assigned this Oct 29, 2016
@rphmeier
Copy link
Contributor

(which is supposedly fixed in tokio-rs/mio#488). Probably can just backport it to our fork once it lands.

@arkpar
Copy link
Collaborator

arkpar commented Oct 29, 2016

Fixed in #2972 and #2973

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

No branches or pull requests

3 participants