！RPC using high cpu & Upgrade to 1.7.8 failed

[w5pand]

Before filing a new issue, please provide the following information.

I'm running:

• Parity version: 1.7.0
• Operating system: Linux（Ubuntu）
• And installed: via installer(.deb)

I have two questions.
1: What makes High Cpu Usage while RPC calling?Because of lower parity version?
2: How to update from version 1.7.0 to 1.7.8?

I set up two private nodes by using POA. High CPU usage when calling Rpc.
So I updated to version 1.7.8, but it doesn't same better.
Maybe something wrong during my upgrading process.

Before the upgrading, there were more than 2 million blocks and db path is "parity2/chainData/networks/parity0/chains/ProductPoA/db/7348aba6abe735d1".

Something changed After that i used command "dpkg -i parity_1.7.8_amd64.deb" and restart the same node. Another db "parity2/chainData/networks/parity0/chains/ProductPoA/db/ dae0d5a8f682ed8a" was created and the block number starts form #1. Below is the log:
`==================================================

Starting Parity/v1.7.8-stable-d5fcf3b-20171025/x86_64-linux-gnu/rustc1.21.0
2017-11-03 20:26:35 Keys path ./chainData/networks/parity0/keys/ProductPoA
2017-11-03 20:26:35 DB path ./chainData/networks/parity0/chains/ProductPoA/db/dae0d5a8f682ed8a
2017-11-03 20:26:35 Path to dapps ./chainData/networks/parity0/dapps
2017-11-03 20:26:35 State DB configuration: fast
2017-11-03 20:26:35 Operating mode: active
2017-11-03 20:26:35 Configured for ProductPoA using AuthorityRound engine
2017-11-03 20:26:36 Removed existing file './chainData/networks/parity0/jsonrpc.ipc'.
2017-11-03 20:26:38 Imported #1 d188…df3d (0 txs, 0.00 Mgas, 0.31 ms, 0.56 KiB)
2017-11-03 20:26:41 Public node URL: enode://9d2ed8ee1612e9de570f1fbf6248c6e360faf79f9b5617d5a170a1bd7c28c592e366bb03076e4db0ccb15b4333de21194804f2d1af56624dc5a38848b5f32283@10.31.22.131:30311
2017-11-03 20:26:42 Imported #2 9eeb…5efe (0 txs, 0.00 Mgas, 0.33 ms, 0.56 KiB)
2017-11-03 20:26:45 Imported #3 15cd…ae54 (0 txs, 0.00 Mgas, 0.28 ms, 0.56 KiB)
2017-11-03 20:26:49 Imported #4 2022…05e5 (0 txs, 0.00 Mgas, 0.30 ms, 0.56 KiB)

===================================================================`

Then I tried to copy the old db fold " 7348aba6abe735d1" to that new one "dae0d5a8f682ed8a" .
It seems that data was imported successfully. But still high cpu usage.

[5chdn]

1: What makes High Cpu Usage while RPC calling?Because of lower parity version?

Can't tell, what exactly are you calling? Can you share your node's logs with -l rpc=trace ?

2: How to update from version 1.7.0 to 1.7.8?

Just installing the new version does the trick, not much more involved.

Another db "parity2/chainData/networks/parity0/chains/ProductPoA/db/ dae0d5a8f682ed8a" was created and the block number starts form #1.

Did you change your chain spec? This indicates a different chain to be worked on.

Can you share your configuration and chain spec?