22.7.0 is our Quarterly release with some big fixes over the previous 22.4.4. This is a recommended update for all users on public networks and those using Bonsai. This release also make many improvements to underlying peering code for better peering on public networks. There are a number of fixes around Merge-related code and the robustness of Besu as a whole.
With the stability of Bonsai in 22.7.0 and some planned optimizations, we are anticipating changing it to the default storage format at some point in the future. We will have more to share on this in the coming months, but nothing more at this time.
This update also includes tweaks and optimizations for memory management, RocksDB, peering default values, and more. See the changelog below and in the last few release candidates for more details.
Bug Fixes
Empty headers are now accepted correctly (per Ethereum p2p Spec) when in a range of headers #4189
Transaction handling will now function correctly when the TTD boundary has been crossed in a Merged network (used to require a restart) #4186
Pandas will now only print once when Merging, not on every startup (sorry panda fans) #4194
Fix for ENR request order handling when peering #4179
Optimizations, Features, & Improvements
New flag (--engine-rpc-enabled) for forcing the Engine API to be present on a network with no TTD set #4190
JEMalloc included in this release. jemalloc is an alternative memory allocator that better handles concurrency and memory fragmentation. Like many other projects, we have discovered that besu benefits from using a modern alternative malloc implementation. In the latest release we have included a preference for the jemalloc library, and have found it to manage rocksdb memory much more effectively. In addition to adding this preference in the *nix besu startup script, jemalloc has been baked into our docker images by default. If you are not running docker besu in a docker container, linux users can leverage jemalloc simply by installing the jemalloc library (which most distributions have a package for)
RocksDB configuration changes. We have spent time researching how to configure our database technology (RocksDB) to gain better performance and address some recent regressions. We are seeing improvements on Block Import times and memory usage in total, so please update to this build if you are experiencing memory challenges.
Add a block to the bad blocks if it did not descend from the terminal block #4080
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
2 years ago
Bumps crypto from 21.10.0-RC1 to 22.7.1-SNAPSHOT.
Release notes
Sourced from crypto's releases.
... (truncated)
Changelog
Sourced from crypto's changelog.
... (truncated)
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)