You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now when compiling the runtime, we immediately allocate all the memory that will be needed (including the heap).
This is the most optimal solution in terms of speed, but in the case of the Wasm node it might be preferable to only allocate memory right before performing a call, and free that memory at the end of the call.
In the Wasm node, this memory is by very far the highest consumption. Each chain uses around 230 MiB of memory, out of which 128 MiB consists in the heap. Note that the figure of 230 MiB is too large because heap pages are currently not properly implemented, but it is sure that 128 MiB is the heap, because that's part of the design of Substrate/Polkadot.
This would decrease the memory usage of each chain, and therefore allow more chains to be started on any given smoldot instance.
The text was updated successfully, but these errors were encountered:
Right now when compiling the runtime, we immediately allocate all the memory that will be needed (including the heap).
This is the most optimal solution in terms of speed, but in the case of the Wasm node it might be preferable to only allocate memory right before performing a call, and free that memory at the end of the call.
In the Wasm node, this memory is by very far the highest consumption. Each chain uses around 230 MiB of memory, out of which 128 MiB consists in the heap. Note that the figure of 230 MiB is too large because heap pages are currently not properly implemented, but it is sure that 128 MiB is the heap, because that's part of the design of Substrate/Polkadot.
This would decrease the memory usage of each chain, and therefore allow more chains to be started on any given smoldot instance.
The text was updated successfully, but these errors were encountered: