You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pulling transactions from getBlocks() and then iterating over them to get transactions receipts should not spike cpu to 100% or take a significantly long time.
Actual behaviour
cpu spikes to 100%, all wss connections lag
Steps to reproduce the behaviour
get transactions from getBlocks and iterate over those with getTransactionReceipt and cpu goes byebye
Backtrace
[backtrace]
The text was updated successfully, but these errors were encountered:
hi, @eyooooo I believe the CPU spike is expected, get receipts is really CPU consuming. We have done the following improvement to get better performance:
provide batch API for get receipts: R4R: add batch query methods #115
You may try the batch API, but if you iterate receipts over all history blocks, I believe the CPU will be still high.
Hi there,
Please note that this is an issue tracker reserved for bug reports and feature requests.
For general questions please use discord or the Ethereum stack exchange at https://ethereum.stackexchange.com.
System information
Geth version:
geth version
geth@GETH:~$ ./geth_linux version
Geth
Version: 1.0.7
Git Commit: f1d92be
Architecture: amd64
Protocol Versions: [65 64 63]
Go Version: go1.15.5
Operating System: linux
GOPATH=
GOROOT=/usr/lib/golang
OS & Version: Windows/Linux/OSX
geth@GETH:~$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.5 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
Commit hash : (if
develop
)Expected behaviour
pulling transactions from getBlocks() and then iterating over them to get transactions receipts should not spike cpu to 100% or take a significantly long time.
Actual behaviour
cpu spikes to 100%, all wss connections lag
Steps to reproduce the behaviour
get transactions from getBlocks and iterate over those with getTransactionReceipt and cpu goes byebye
Backtrace
The text was updated successfully, but these errors were encountered: