Summary

  • APNIC Blog published Matheus Stolet’s guest post on 14 August 2026. It presents Chamelio as an attempt to escape a familiar cloud-network trade-off: per-VM stacks protect customization and isolation, while a shared host datapath can use CPU capacity more efficiently.
  • The post says tenants supply eBPF handlers for receive, scheduled-send and dequeue work; safety verification remains in a provider control plane, while complex or state-heavy work stays on a VM-resident slow path. It reports 1.96× per-core throughput against siloed stacks, 9.2 million requests per second for a custom TCP case, and a 26-microsecond 99th-percentile RTT.

Evidence boundary

The APNIC page is explicitly labelled Guest Post and says the author’s views do not necessarily represent APNIC. It reports an architecture and benchmark claims, not an APNIC service, customer deployment, production availability, code release, independent replication or a general cloud-performance result.

Sources