Does the Component Model Require Extra Copying?
summary
Argues that the Component Model need not add copying by showing concrete mechanisms in 0.2 and 0.3: value types vs resource types explain where the baseline copy happens (e.g., lists written via a caller-supplied realloc), switching resources for HTTP middleware avoids full request copies, and stream handles and async reads let kernels copy directly into linear memory so large bodies stream without extra copies. Also proposes shared-heaps / mappable byte arrays and notes Fastly can start sandboxes in 35 microseconds.
AI-written summary · about
chapters (7)
- 0:00Why WebAssembly?
- 2:21The component model
- 6:06Linking and performance
- 10:03Value types and resources
- 14:36Streams and WASI 0.3
- 19:03Future memory strategies
- 25:40Conclusion and Q&A
related talks
30mComponent Model in Software Defined Vehicles
38mTowards a Component Model 1.0
54mComponents for the Web: The Client-side Component Model (ccm)
35mComposable Concurrency for WebAssembly Components
30mKeynote: What is a Component (and Why)?
31mWebAssembly Component Model: Enhancing Security, Productivity, and...
32mThreading the needle with concurrency and parallelism in the Component Model
36mBootstrapping Ecosystems: Unveiling the Power of the Component Model