跳到正文
研踪PaperTrail

论文库

检索计算机领域论文,按研究方向、作者或关键词筛选。

部分采集异常
正在读取账号与研究记录…

全站更新概况

+479新增论文
+361其中 AI 相关
+63已有论文修订
+93新增 AI 导读

arXiv 最近完成扫描:2026-11-16 01:34 · 全站最近入库:2026-11-16 13:44各信源进度 →

统计口径与数据新鲜度

统计 2026-11-15 20:30 — 2026-11-16 20:30(北京时间) · 点击数字查看对应简报;AI 相关包含在新增论文内。

最近完成检查:2026-11-16 01:34最近发现新增版本:2026-11-16 13:44库内论文最新更新时间:2026-11-14 02:59

每分钟刷新已保存的数据。空检查不代表采集异常;新收录可能包含历史论文。AI 导读按新增版本计数。

23,827 已收录论文19,941 AI 相关6,921 有修订112 HF 社区发现

浏览论文库

时间范围跟随排序:版本更新、本站收录或首次发表。最新收录可能包含历史论文。部分信源异常,查看状态 →

找到 1 篇论文 · 按版本更新时间排序上轮扫描起点 2026-11-16 01:33(北京时间)
新论文 · v1arXiv:2611.12620

Reducing Cold-Start Latency on the WebAssembly Edge via Locality and Network-Aware Scheduling

Michiel Van Kenhove, Emiel Sucaet, José Santos, Filip De Turck, Bruno Volckaert, Merlijn Sebrechts

原文摘要

Edge computing places computation closer to users and data sources, but introduces heterogeneous hardware, limited resources, and variable network conditions. WebAssembly (Wasm) is increasingly considered for these environments because modules are compact, portable, and quick to start. However, cold-start latency remains a challenge: when a worker node does not yet hold the required artifact, it must fetch it before execution, adding transfer overhead that directly increases the end-to-end (E2E) latency, especially for large artifacts or slow network links. At the same time, the geographical distance between the requester and the assigned worker independently contributes to latency through network routing overhead. Together, artifact locality and network proximity do not always point to the same placement decision, and naive scheduling strategies fail to account for either. This work extends a Wasm-native edge orchestrator with state-aware scheduling strategies that jointly optimize for both objectives. Evaluation on a Raspberry Pi testbed with emulated regional network latency shows that a hybrid scheduler combining cache-state and network-proximity signals reduces mean E2E latency by up to 40.8% compared to a default round-robin baseline. Artifact locality-aware placement is most effective when artifacts are large or repeatedly requested, while network-aware placement dominates when artifacts are small and routing latency has a larger relative effect, but combining both objectives consistently yields the lowest E2E latency across diverse edge workloads.

cs.NI · cs.SE