ljedrz

Since this is a crypto-specific issue I'm not going to resolve it using my usual engineering magic. @howardwu your call

Some open questions: - should we distinguish between production and dev modes? - should we consider the network IDs? - should the creation of the file path be dedicated to...

Addressed the points in the previous comment.

Rebased.

> under what conditions do you see the reduction? Is it just normal operation of a node minus any load? The difference was measured for a `--dev 2` node which...

Observations based on devnet metrics: - memory use is a bit lower, but there is still growth - log frequency is up, suggesting higher average throughput - average block lag...

Update: the same can be done with `WriteOptions`; the win is smaller, as we write less frequently.

Would the following tweak suffice? ``` diff --git a/synthesizer/process/src/stack/execute.rs b/synthesizer/process/src/stack/execute.rs index 4a2936d91..3c4331c79 100644 --- a/synthesizer/process/src/stack/execute.rs +++ b/synthesizer/process/src/stack/execute.rs @@ -421,8 +421,9 @@ impl StackExecute for Stack { if matches!(registers.call_stack(), CallStack::Synthesize(..)) ||...

I see that the issue with connecting to the outside world is resolved, nice; as for the other listed issues: 1. Can you please post the full `tokio` error you...

This looks like some bug between `libp2p` and `tokio`, most likely `libp2p_swarm` specifically; we've been planning to upgrade `libp2p` and `tokio` for a while now: https://github.com/rs-ipfs/rust-ipfs/pull/431, just waiting for the...