focalinterest.net

AI Summary of Scholarly Research

This page presents an AI-generated summary of a published research paper. The original authors did not write or review this article. [See full disclosure ↓]

WaSC decouples WebAssembly system access with low startup latency

Written by

editor@focalinterest.com

in

Research area:computer-science-aialgorithms-theory

What the study found

The study found that WaSC, a secure container runtime, hardens WebAssembly system isolation by decoupling the system interface into a virtualization-based daemon. The authors report that this preserves function-level startup time and memory use while protecting the system interface with machine-level isolation.

Why the authors say this matters

The authors say this matters because WebAssembly (WASM), a web standard for running code in a sandboxed environment, is emerging as an alternative to containers in serverless computing, but the WASM System Interface (WASI) does not guarantee isolation from the host kernel. The study suggests WaSC addresses that gap while keeping some of the efficiency advantages associated with WASM.

What the researchers tested

The researchers introduced WaSC and evaluated it with microbenchmarks and application benchmarks. They compared its performance with Firecracker, a secure container runtime, and examined startup latency, memory footprint, system interface call overhead, and application runtime behavior.

What worked and what didn't

WaSC achieved a 99th-percentile startup latency of 15 ms and a memory footprint of about 10 MB. Compared with Firecracker, it achieved 3× memory density on a single physical machine. The study also found a 3.2× slowdown for WASI calls along the virtualization-based daemon path, and SQLite speedtest1 showed an average 80% increase in runtime.

What to keep in mind

The abstract does not describe security limitations beyond noting that WASI does not guarantee isolation from the host kernel. It also does not provide details on which workloads were included beyond the mention of microbenchmarks, application benchmarks, and SQLite speedtest1.

Key points

  • WaSC hardens WebAssembly system isolation by moving the system interface into a virtualization-based daemon.
  • The authors report 15 ms 99th-percentile startup latency and about 10 MB memory footprint.
  • WaSC achieves 3× memory density compared with Firecracker on a single physical machine.
  • WASI calls through the daemon path are reported to slow down by 3.2×.
  • SQLite speedtest1 shows an average 80% increase in runtime.

Disclosure

Research title:
WaSC decouples WebAssembly system access with low startup latency
Authors:
Xingzi Yu, Tianlei Xiong, Wei Tang, Yufan Jiang, Zhixiang Wei, Hao Wang, Chen Chen, Yun Wang, Bo Peng, Zhengwei Qi
Institutions:
Antea Group (France), Shanghai Jiao Tong University, Shanghai Jiao Tong University, Shanghai Jiao Tong University, Shanghai Jiao Tong University, Shanghai Jiao Tong University, Shanghai Jiao Tong University, Shanghai Jiao Tong University, Shanghai Jiao Tong University, Stevens Institute of Technology
Publication date:
2026-02-23
DOI:
10.1145/3795882
OpenAlex record:
View
AI provenance: This post was generated by gpt-5.4-mini (OpenAI). The original authors did not write or review this post.

More posts