cerc-io/lighthouse
16
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Only perform malloc tuning for beacon node (#2397)

Browse Source 
## Issue Addressed

NA

## Proposed Changes

Only run `configure_memory_alllocator` for the BN process.

I noticed that VC memory usage increases significantly with the new malloc tuning parameters. This was also raised by a user on [r/ethstaker](https://www.reddit.com/r/ethstaker/comments/nr8998/lighthouse_prerelease_v140rc0/h0fnt9l?utm_source=share&utm_medium=web2x&context=3).

There wasn't any issue with memory usage by the VC before we implemented #2296, so I think we were a bit overzealous when we allowed these changes to affect it. This PR allows things that weren't broken to remain unfixed.

## Additional Info

NA
This commit is contained in:
Paul Hauner 2021-06-07 02:34:10 +00:00
parent 93100f221f
commit 4a6f2fac81
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
lighthouse/src/main.rs
View File

@ -165,7 +165,11 @@ fn main() {
// Configure the allocator early in the process, before it has the chance to use the default values for
// anything important.
if !matches.is_present(DISABLE_MALLOC_TUNING_FLAG) {
//
// Only apply this optimization for the beacon node. It's the only process with a substantial
// memory footprint.
let is_beacon_node = matches.subcommand_name() == Some("beacon_node");
if is_beacon_node && !matches.is_present(DISABLE_MALLOC_TUNING_FLAG) {
if let Err(e) = configure_memory_allocator() {
eprintln!(
"Unable to configure the memory allocator: {} \n\