Wasmer Issue Tracking

[yun-yeo]

Memory leak

Reusing wamser's module is definitely causing memory leak but this adoption comes from performance improvement.

• Linux memory leak - wasmer 2.x wasmerio/wasmer#2780
• Allow decomposition and composition of Modules without serialization wasmerio/wasmer#1933
• Module file cache cost CosmWasm/cosmwasm#603

When we rollback cosmwasm cache to store serialized artifact, memory leak is gone.
terra-money/cosmwasm@16eae76

Frame error (aka. Poison error)

• Failed to instantiate a deserialized Module compiled with the Dylib engine wasmerio/wasmer#2434 (comment)

Wasmer bump related issues

The file cache created from wasmer@v2.0.0 cannot be used from wasmer@v2.1.x or wasmer@v2.2.x.

• Serialized module stability wasmerio/wasmer#2781

[yun-yeo]

CosmWasm teams benchmark result - CosmWasm/cosmwasm#657
When we revert CosmWasm cache to use serialization again, the performance degradation seems huge

Cache/instantiate from fs                                                                            
                        time:   [3.8578 ms 4.0083 ms 4.1232 ms]
                        change: [-33.227% -30.126% -27.424%] (p = 0.00 < 0.05)
                        Performance has improved.
Cache/instantiate from memory                                                                            
                        time:   [2.5783 ms 2.6381 ms 2.6863 ms]
                        change: [+3559.6% +3718.3% +3840.8%] (p = 0.00 < 0.05)
                        Performance has regressed.
Cache/instantiate from pinned memory                                                                            
                        time:   [2.5794 ms 2.6677 ms 2.7162 ms]
                        change: [+3755.9% +3851.0% +3920.2%] (p = 0.00 < 0.05)
                        Performance has regressed.

[yun-yeo]

To avoid performance degradation, changed cache strategy to cache both artifact and module and refresh cached module from a background thread with cached artifact - terra-money/cosmwasm@78026fd

• Load
  If we have refresh background thread, then just return cached module.
  If we don't have refresh background thread, then create refresh thread and return cached module.

refresh thread deserializes artifact into module and replace cached module.