Skip to content

OutOfMemory Issues when running chain #9016

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

Closed
maxp1256 opened this issue Jan 20, 2025 · 5 comments
Closed

OutOfMemory Issues when running chain #9016

maxp1256 opened this issue Jan 20, 2025 · 5 comments

Comments

@maxp1256
Copy link

Hello
I'm trying to run teku (chain) but I'm experiencing OutOfMemory errors. When I set TEKU_OPTS to 10 or -Xmx12G it's working, but there is a very high cpu usage (>90%) at a 4 core Hyper-V-VM on a i7-7740X.

Is this a normal behaviour? Are there any further recommendations?

@rolfyone
Copy link
Contributor

hey there, thanks for raising this.
Initially can we ask what version of teku, and also what -Xmx you had with OOM, and other command arguments that you may have set when running?
Operating system would also be of interest...

@maxp1256
Copy link
Author

maxp1256 commented Jan 20, 2025

Hello @rolfyone,
I'm using latest teku 24.6.1 (sorry thought that it was the latest one - I'll check again after updating)

I got an OOM with 8G, 10G was stable and 12G also, but CPU usage didn't change.

OS is Win10 22H2 (with latest updates)

Java openjdk 19.0.2 2023-01-17
Zulu19.32+13-CA

Arguments are the default one for chain only (--network=mainnet --eth1-endpoint --rest-api-enabled=true --metrics-enabled --ee-endpoint --p2p-peer-lower-bound=120 --p2p-peer-upper-bound=150)

I've raised cpu cores from 4 to 6 in hyper-v, so CPU usage has lowered to 25-75%

I'm still getting sometimes a "Late Block Import" with arrival 2000-3198 ms and processed 1500ms-3200ms

@rolfyone
Copy link
Contributor

Hey, my expectation would be that 8G would be fine on mainnet currently as long as there's adequate CPU.
I'd definitely recommend updating beyond 24.6.1, there's been a number of enhancements and security fixes in the last six months. It will be worth looking at the 'breaking changes' since 24.6.1.

@rolfyone
Copy link
Contributor

@maxp1256 is this still happening ? any more information?

@rolfyone
Copy link
Contributor

Closing, assuming we're resolved here but feel free to open a new issue if we get more information.

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

2 participants