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

Very high CPU usage while running Parity on Windows #7958

Closed
duanehutchins opened this issue Feb 20, 2018 · 1 comment
Closed

Very high CPU usage while running Parity on Windows #7958

duanehutchins opened this issue Feb 20, 2018 · 1 comment
Labels
M4-core ⛓ Core client code / Rust. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known.
Milestone

Comments

@duanehutchins
Copy link

I'm running:

  • Which Parity version?: 1.9.3-beta
  • Which operating system?: Windows 10 x64
  • How installed?: via installer
  • Are you fully synchronized?: yes
  • Which network are you connected to?: ethereum
  • Did you try to restart the node?: yes

Steps to duplicate:

  • Start parity 1.9.3 with default options

What happens:

  • Moderate-to-high CPU usage (30% - 99%)
  • Screenshot: parity-cpu-usage

What is expected to happen:

  • Low-to-moderate CPU usage (5% - 30%)

This higher-than-normal CPU usage started happening with v1.9.0 and is still happening with v1.9.3-beta. Testing with v1.8.10 and v1.7.13, I do not have high CPU usage.

I already tried:

  • Restarting the node
  • Restarting the computer
  • Deleting the DB and resyncing from scratch
  • Disabling the UI, dapps, jsonrpc, warp, ancient-blocks, and hardware-wallets
    • Disabling hardware-wallets seemed to reduce the CPU usage somewhat, but it is still very much higher than pre v1.9 and will still cap my cpu usage to 100%
    • Disabling the other options did not seem to have a noticeable impact on CPU usage.

Notes:

  • It sometimes take 5-20 minutes to get high cpu usage while running v1.9.x, but it then stays high after that point.
  • This does not happen to me while running v1.8.x or v1.7.x
  • Looking at the logs, I do not see any apparent causes. Transactions are being imported and verified as normal, but then the cpu spikes and stays high even though no obvious changes within the logs.
  • I'm pasting a snip from the log below. Around 16:26:12 the CPU usage spiked to 100% and then stayed high (+80%) after that. I do not see anything out of the ordinary at that time. Ten minutes later, it was still at 90%.

Any ideas? Any help would be appreciated greatly.

Parity log snippet:
2018-02-20 16:23:16  Verifier #1 INFO import  Imported #5126554 38fe…ee06 (125 txs, 8.00 Mgas, 128.30 ms, 23.40 KiB)
2018-02-20 16:23:21  Verifier #1 INFO import  Imported #5126555 3623…28fc (151 txs, 6.01 Mgas, 141.21 ms, 22.21 KiB)
2018-02-20 16:23:32  IO Worker #2 INFO import    23/25 peers      6 MiB chain   99 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  0 req/s, 106 µs
2018-02-20 16:23:51  Verifier #1 INFO import  Imported #5126556 4280…aca2 (94 txs, 3.58 Mgas, 90.79 ms, 15.45 KiB)
2018-02-20 16:23:54  Verifier #1 INFO import  Imported #5126556 ef02…7ffe (133 txs, 7.87 Mgas, 151.72 ms, 23.13 KiB)
2018-02-20 16:23:56  Verifier #1 INFO import  Imported #5126557 d3ef…fae3 (114 txs, 7.98 Mgas, 228.42 ms, 18.06 KiB)
2018-02-20 16:24:03  IO Worker #3 INFO import    21/25 peers      4 MiB chain   99 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  3 req/s, 111 µs
2018-02-20 16:24:03  IO Worker #2 INFO import    21/25 peers      4 MiB chain   99 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  3 req/s, 111 µs
2018-02-20 16:24:06  Verifier #3 INFO import  Imported #5126558 686a…adaf (172 txs, 7.86 Mgas, 295.20 ms, 29.43 KiB)
2018-02-20 16:24:08  Verifier #0 INFO import  Imported #5126559 1d3b…b248 (116 txs, 7.82 Mgas, 120.36 ms, 20.99 KiB)
2018-02-20 16:24:20  Verifier #0 INFO import  Imported #5126560 1435…ff95 (32 txs, 1.10 Mgas, 19.82 ms, 5.11 KiB)
2018-02-20 16:24:37  IO Worker #3 INFO import    22/25 peers      6 MiB chain   97 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  3 req/s,  81 µs
2018-02-20 16:25:03  Verifier #1 INFO import  Imported #5126561 543e…dce6 (121 txs, 7.73 Mgas, 112.36 ms, 25.86 KiB)
2018-02-20 16:25:07  IO Worker #2 INFO import    23/25 peers      7 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  3 req/s, 115 µs
2018-02-20 16:25:10  Verifier #1 INFO import  Imported #5126562 1d3e…1be9 (193 txs, 7.98 Mgas, 199.16 ms, 27.60 KiB)
2018-02-20 16:25:17  Verifier #1 INFO import  Imported #5126563 2dfe…9250 (197 txs, 7.12 Mgas, 171.96 ms, 29.20 KiB)
2018-02-20 16:25:30  Verifier #1 INFO import  Imported #5126564 3e01…f37b (70 txs, 3.91 Mgas, 57.19 ms, 11.34 KiB)
2018-02-20 16:25:34  Verifier #1 INFO import  Imported #5126563 a8cf…3385 (106 txs, 7.98 Mgas, 246.13 ms, 17.11 KiB)
2018-02-20 16:25:39  IO Worker #2 INFO import    24/25 peers      6 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  1 req/s, 104 µs
2018-02-20 16:25:39  Verifier #1 INFO import  Imported #5126565 0801…ac3f (47 txs, 1.41 Mgas, 49.01 ms, 6.60 KiB)
2018-02-20 16:25:47  Verifier #1 INFO import  Imported #5126566 ac07…617d (151 txs, 7.97 Mgas, 193.91 ms, 25.16 KiB)
2018-02-20 16:26:02  Verifier #1 INFO import  Imported #5126567 fbf0…5a9c (113 txs, 7.99 Mgas, 109.02 ms, 21.62 KiB)
2018-02-20 16:26:12  IO Worker #1 INFO import    23/25 peers      6 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  2 req/s, 116 µs
2018-02-20 16:26:18  Verifier #1 INFO import  Imported #5126568 7aa4…da63 (124 txs, 7.69 Mgas, 189.06 ms, 22.32 KiB)
2018-02-20 16:26:40  Verifier #1 INFO import  Imported #5126569 8de3…1380 (155 txs, 7.75 Mgas, 154.71 ms, 22.51 KiB)
2018-02-20 16:26:47  Verifier #1 INFO import  Imported #5126570 6b60…5123 (164 txs, 7.99 Mgas, 177.30 ms, 21.23 KiB)
2018-02-20 16:26:47  IO Worker #0 INFO import    23/25 peers      6 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  2 req/s,  81 µs
2018-02-20 16:26:49  Verifier #1 INFO import  Imported #5126571 ba82…bfef (64 txs, 2.40 Mgas, 49.13 ms, 8.52 KiB)
2018-02-20 16:26:54  Verifier #1 INFO import  Imported #5126572 b20f…0ece (23 txs, 0.70 Mgas, 21.67 ms, 3.22 KiB)
2018-02-20 16:26:58  Verifier #3 INFO import  Imported #5126572 93d3…d9f0 (23 txs, 0.70 Mgas, 22.19 ms, 3.22 KiB)
2018-02-20 16:27:05  Verifier #1 INFO import  Imported #5126574 1c3d…3caf (74 txs, 7.98 Mgas, 95.80 ms, 10.39 KiB) + another 1 block(s) containing 57 tx(s)
2018-02-20 16:27:16  Verifier #1 INFO import  Imported #5126575 9c75…7b22 (158 txs, 7.98 Mgas, 246.53 ms, 19.99 KiB)
2018-02-20 16:27:22  IO Worker #1 INFO import    24/25 peers      5 MiB chain   97 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  4 req/s,  73 µs
2018-02-20 16:27:40  Verifier #2 INFO import  Imported #5126576 df77…ca58 (149 txs, 7.97 Mgas, 293.96 ms, 20.84 KiB)
2018-02-20 16:27:57  IO Worker #3 INFO import    23/25 peers      5 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  2 req/s, 102 µs
2018-02-20 16:28:11  Verifier #2 INFO import  Imported #5126577 f3d1…ef16 (188 txs, 7.88 Mgas, 231.41 ms, 30.25 KiB)
2018-02-20 16:28:27  IO Worker #2 INFO import    23/25 peers      4 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  2 req/s,  95 µs
2018-02-20 16:28:32  Verifier #2 INFO import  Imported #5126578 5be8…0789 (175 txs, 7.82 Mgas, 238.25 ms, 26.97 KiB)
2018-02-20 16:28:57  IO Worker #3 INFO import    24/25 peers      5 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  1 req/s, 110 µs
2018-02-20 16:29:32  IO Worker #1 INFO import    24/25 peers      5 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  2 req/s,  98 µs
2018-02-20 16:29:36  Verifier #2 INFO import  Imported #5126579 15ee…e254 (137 txs, 7.99 Mgas, 164.54 ms, 26.52 KiB)
2018-02-20 16:30:07  IO Worker #3 INFO import    24/25 peers      5 MiB chain   98 MiB db  0 bytes queue   22 KiB sync  RPC:  1 conn,  2 req/s, 107 µs
2018-02-20 16:30:17  Verifier #0 INFO import  Imported #5126581 ff12…db4c (190 txs, 7.96 Mgas, 274.02 ms, 27.47 KiB) + another 1 block(s) containing 199 tx(s)
@5chdn 5chdn added Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. M4-core ⛓ Core client code / Rust. labels Feb 21, 2018
@5chdn 5chdn added this to the 1.10 milestone Feb 21, 2018
@5chdn 5chdn modified the milestones: 1.10, 1.11 Mar 1, 2018
@5chdn 5chdn modified the milestones: 1.11, 1.12 Apr 24, 2018
@5chdn
Copy link
Contributor

5chdn commented Jun 24, 2018

closing in favor of #8696

@5chdn 5chdn closed this as completed Jun 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
M4-core ⛓ Core client code / Rust. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known.
Projects
None yet
Development

No branches or pull requests

2 participants