FVM (Experimental) Mainnet v15 Testing & Feedback

[jennijuju]

🍼 Filecoin v16 Skyr upgrade will introduce Filecoin non-programmable WASM-based Filecoin Virtual Machine (FVM) to Filecoin mainnet. Upon the v16 Skyr upgrade, Mainnet will atomically switch from the current built-in VMs to the WASM-based reference FVM. A new gas model will be activated that accounts for actual WASM execution costs. Only built-in actors will be supported at this time. This upgrade will mark the completeness of FVM development Milestone 1.

That being said, before fully switch the network using FVM and built-in actor, we'd like to make sure it works with the existing the network. Meaning, for any implementation that iterates the FVM and built-in actor, the node should be able to syncing the current network, SPs may producing blocks, proving the storage, sealing new sectors and making deals, and the rest of the network operation, including msig, payment channel, verifreg and so on should remain functional.

Regular Operations

To start with, update your nodes to lotus v1.15.1-rc2, set the LOTUS_USE_FVM_EXPERIMENTAL=1 and restart your node.

Note: the current lotus build can only sync mainnet using FVM!

Then make a copy of the FVM 0.5 Checklist, ✅ boxes off as you perform the operation more than once and leave any comments/feedback in the call out session!

⚠️ Reminders and Risk Mitigations

• Questions are welcomed in this discussion, the team will be monitoring this discussion and check-in regularly.
• Issues can be reported in the https://github.com/filecoin-project/lotus/issues. Issues should be submitted with:
  • daemon logs
  • go routine dumps ** lotus pprof goroutines**
  • the operation/step at which the problem occurred
  • The stack trace or logs as relevant. As always, for large log files, you may upload it in this gdrive folder and link it in the issue!
• If you think FVM is not working well, keep all the logs for describing the issue, then disable LOTUS_USE_FVM_EXPERIMENTAL and restart your node!

[jennijuju]

Ozzy's FVM 0.5 Checklist

(order doesn't matter)

• Node stays in sync.
• Pledge a new sector.
• Extend a sector expiration.
• Make a snap deal.
• Add a new control address
• Make a paid retrieval deal (self dealing if there is no retrieval client!).
• Make a WindowPoSt.
• Get luck and mine a new block!
• Collect the following metrics
• Disable FVM and restart the node, operations remain functional.

	FVM	Lotus Legacy VM	Perf +- %
block validation time
memory usage
CPU usage

Any callouts

• I'm excited for FVM!
  

[TippyFlitsUK]

TippyFlits FVM 0.5 Checklist

• Node stays in sync.
• Pledge a new sector.
• Extend a sector expiration.
• Make a snap deal.
• Add a new control address
• Make a paid retrieval deal (self dealing if there is no retrieval client!).
• Make a WindowPoSt.
• Get luck and mine a new block!
• Collect the following metrics
• Disable FVM and restart the node, operations remain functional.

	FVM	Lotus Legacy VM	Perf +- %
block validation time			Unchanged
memory usage			Unchanged
CPU usage			Unchanged

[jennijuju]

@TippyFlitsUK we may have to uncheck 1 box lolol

[TippyFlitsUK]

..... so close to a full house!!

[Angelo-gh3990]

Angelo's FVM 0.5 Checklist

• Node stays in sync.
• Pledge a new sector.
• Extend a sector expiration.
• Make a snap deal.
• Add a new control address
• Make a paid retrieval deal (self dealing if there is no retrieval client!).
• Make a WindowPoSt.
• Get luck and mine a new block!
• Collect the following metrics
• Disable FVM and restart the node, operations remain functional.

	FVM	Lotus Legacy VM	Perf +- %
block validation time
memory usage
CPU usage

Updates will follow!

[rjan90]

Phi-rjan´s FVM 0.5 Checklist

• Node stays in sync.
• Pledge a new sector.
• Extend a sector expiration.
• Make a snap deal.
• Add a new control address
• Make a paid retrieval deal (self dealing if there is no retrieval client!).
• Make a WindowPoSt.
• Get lucky and mine a new block!
• Disable FVM and restart the node, operations remain functional.
• Collect the following metrics

	FVM	Lotus Legacy VM	Perf +- %
block validation time	0.498s	0.503s	-
memory usage	16GiB	16GiB	-
CPU usage	-	-	unchanged

[jamerduhgamer]

James' FVM 0.5 Checklist

• Node stays in sync.
• Pledge a new sector.
• Extend a sector expiration.
• Make a snap deal.
• Add a new control address
• Make a paid retrieval deal (self dealing if there is no retrieval client!).
• Make a WindowPoSt.
• Get luck and mine a new block!
• Disable FVM and restart the node, operations remain functional.
• Collect the following metrics

	FVM	Lotus Legacy VM	Perf +- %
block validation time	<1 second	<1 second	0%
memory usage	~14 GiB	~14 GiB	0%
CPU usage	~3 threads	~3 threads	0%

[jamerduhgamer]

Ran into an issue with sectors expiring immediately upon pledging a new sector.

[jamerduhgamer]

Figured out the issue with the sectors expiring immediately.

[jennijuju]

v1.15.1-rc3 is out with the actor bug fix!

[Reiers]

Reiers´s FVM 0.5 Checklist

• Node stays in sync.
• Pledge a new sector.
• Extend a sector expiration.
• Make a snap deal.
• Add a new control address
• Make a paid retrieval deal (self dealing if there is no retrieval client!).
• Make a WindowPoSt.
• Get lucky and mine a new block!
• Disable FVM and restart the node, operations remain functional.
• Collect the following metrics

	FVM	Lotus Legacy VM	Perf +- %
block validation time		TBD
memory usage		TBD
CPU usage

Will have production upgraded by the end of the day.

[Reiers]

v1.15.1-rc4 is out.

[cryptowhizzard]

Wijnand's FVM Checklist. ( Running v1.15.1-rc4 )

• Node stays in sync.
• Pledge a new sector.
• Extend a sector expiration.
• Make a snap deal.
• Add a new control address - [X]
• Make a paid retrieval deal (self dealing if there is no retrieval client!).
• [X ] Make a WindowPoSt.
• Get luck and mine a new block!
• Collect the following metrics
• Disable FVM and restart the node, operations remain functional.

	FVM	Lotus Legacy VM	Perf +- %
block validation time	No Change
memory usage	No Change
CPU usage	No Change

More updates coming ;-)