From 55a71c4c1a45643ce4d5181352f7b799e244efd7 Mon Sep 17 00:00:00 2001 From: Steven Allen Date: Wed, 19 Jun 2024 09:49:45 -0700 Subject: [PATCH] chore: update changelog to record FVM concurrency changes --- CHANGELOG.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 95ad61a383e..5add9315c1c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -34,6 +34,16 @@ There is no change in the behaviour when a call returns an error, as the error o ## New features +### FVM RPC Concurrent Requests + +The default maximum FVM concurrency (`LOTUS_FVM_CONCURRENCY`) has increased from 4 to the number of available CPU threads. Furthermore, the FVM now allocates `LOTUS_FVM_CONCURRENCY` OS-level threads with 64MiB stacks (in 1.26, we allocated one thread per CPU core regardless of the value of `LOTUS_FVM_CONCURRENCY`). + +Impact: + +1. This will increase memory usage for nodes specifying a higher `LOTUS_FVM_CONCURRENCY` than the number of CPU threads they have available. +2. This will allow such nodes to actually take advantage of this higher concurrency limit where the concurrency was previously capped at the number of available CPU threads. + + ## Improvements # v1.27.0 / 2024-05-27