Investigating the Impact of Isolation on Synchronized Benchmarks的研究
Investigating the Impact of Isolation on Synchronized Benchmarks
AI总结:
本研究评估了cgroups、Docker和Firecracker三种隔离策略对同步基准测试中VM内部资源争用的影响,发现进程隔离通常能降低误报,但Docker容器例外,建议同步工作负载采用进程隔离。
摘要:
云环境中的基准测试因多租户资源争用而产生性能多变性。Duet benchmarking通过在同一VM上并发运行两个工作负载版本,使其暴露于相同的外部干扰中来缓解此问题。然而,同步工作负载间的VM内部争用需要额外的隔离机制。本研究评估了三种此类策略:cgroups和CPU pinning、Docker容器以及Firecracker MicroVMs。我们通过在duet设置下运行基准测试并配合噪声生成器,将所有策略与未隔离的基线实验进行比较。该噪声生成器“窃取”计算资源以降低性能测量。所有实验在噪声影响下显示出不同的延迟分布,但结果表明,进程隔离通常降低了误报,Docker容器实验除外。尽管Docker容器内部依赖cgroups和CPU pinning,但它们更易受噪声影响导致性能下降。因此,我们建议对同步工作负载使用进程隔离,Docker容器除外。
英文摘要:
Benchmarking in cloud environments suffers from performance variability from multi-tenant resource contention. Duet benchmarking mitigates this by running two workload versions concurrently on the same VM, exposing them to identical external interference. However, intra-VM contention between synchronized workloads necessitates additional isolation mechanisms. This work evaluates three such strategies: cgroups and CPU pinning, Docker containers, and Firecracker MicroVMs. We compare all strategies with an unisolated baseline experiment, by running benchmarks with a duet setup alongside a noise generator. This noise generator "steals" compute resources to degrade performance measurements. All experiments showed different latency distributions while under the effects of noise generation, but results show that process isolation generally lowered false positives, except for our experiments with Docker containers. Even though Docker containers rely internally on cgroups and CPU pinning, they were more susceptible to performance degradation due to noise influence. Therefore, we recommend to use process isolation for synchronized workloads, with the exception of Docker containers.
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。