We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Got different behavior of nodes regarding process_heap_bytes
here we batch ~4 messages per ckzg.verifyCellKzgProofBatch() call
ckzg.verifyCellKzgProofBatch()
here we batch ~10 messages per ckzg.verifyCellKzgProofBatch() call
here we batch ~13.5 messages per ckzg.verifyCellKzgProofBatch() call
here we batch ~15 messages per ckzg.verifyCellKzgProofBatch() call
it should not grow over time, ideally should be ~<= 13GB, similar to a mainnet node subscribing to all subnets
No response
Linux
te/validate_data_column_sidecar_in_batch
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
it also happens on peerDAS so it's an issue of c-kgz verifyCellKzgProofBatch itself
peerDAS
verifyCellKzgProofBatch
No branches or pull requests
Describe the bug
Got different behavior of nodes regarding process_heap_bytes
here we batch ~4 messages per
ckzg.verifyCellKzgProofBatch()
callhere we batch ~10 messages per
ckzg.verifyCellKzgProofBatch()
callhere we batch ~13.5 messages per
ckzg.verifyCellKzgProofBatch()
callhere we batch ~15 messages per
ckzg.verifyCellKzgProofBatch()
callExpected behavior
it should not grow over time, ideally should be ~<= 13GB, similar to a mainnet node subscribing to all subnets
Steps to reproduce
No response
Additional context
No response
Operating system
Linux
Lodestar version or commit hash
te/validate_data_column_sidecar_in_batch
The text was updated successfully, but these errors were encountered: