high cpu usage and iowait when idle

[goldsquid]

I'm using 2 server grade nvme in raid0 at 30% capcity running op-bnb/geth and op-bnb/node seeing 3% iowait and constant read access when runniung the archive node from the snapshot.

comparing that with optimism rollups of the same datadir size that's concerning as other rollups using hash state scheme and leveldb as backend are basically idle on the disk. I'm running the latest release 0.3.0 from last week.

I doubt that I can just switch out op-bnb for op-geth due to tuned block gas parameters.

[goldsquid]

another issue is that after a few days of running without issues it stops progressing for me. I checked the logs. no error. went though 4 GB of logs for 3 days. blocknumber is not advancing.

[STdevK]

What's your node start-up command?

[goldsquid]

I use this docker-compose https://github.com/StakeSquid/ethereum-rpc-docker/blob/main/op-bnb.yml which is copied from the reference docker-compose with the variables filled in.

[krish-nr]

another issue is that after a few days of running without issues it stops progressing for me. I checked the logs. no error. went though 4 GB of logs for 3 days. blocknumber is not advancing.

Could you pls check if there's keyword "Database compacting, degraded performance" in geth log?

[goldsquid]

The keywords are not in the log

On Wed, 3 Apr 2024 at 15:15, krish-z @.***> wrote:

another issue is that after a few days of running without issues it stops progressing for me. I checked the logs. no error. went though 4 GB of logs for 3 days. blocknumber is not advancing.

Could you pls check if there's keyword "Database compacting, degraded performance" in geth log?

— Reply to this email directly, view it on GitHub https://github.com/bnb-chain/opbnb/issues/173#issuecomment-2033870509, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDFLZD2MWDYBGPMKWLTI3KLY3O3BRAVCNFSM6AAAAABFN2Y7IKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTHA3TANJQHE . You are receiving this because you authored the thread.Message ID: @.***>

[krish-nr]

@goldsquid could you paste the recent logs from both op-node and op-geth here so that we can analyze the issue?

[github-actions[bot]]

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

The issue is closed due to long inactivity. You can reopen it for further questions or comments.