跳到正文
研踪PaperTrail
← 研踪 PaperTrail

arXiv:2611.21442 · v1

The Bipartible Architecture Pattern: Transparently Directing HTTP Requests over InfiniBand

首次提交 2026-11-17 01:30
版本更新 2026-11-17 01:30
雷达观测 2026-11-17 16:10
arXiv ↗PDF ↗

摘要

Large-scale compute (HPC) systems with coherent-memory workloads often deploy InfiniBand (IB) networks for high-bandwidth and low-latency inter-node and storage communication. A separate TCP network is typically used for control-plane and general-purpose communication. The last decade has seen the rise of cloud-native software patterns. These patterns are characterized by container-based software distribution and inter-node and storage communication over TCP/IP. In an unoptimized HPC environment, a cloud-native workload will typically use HTTP for some or all communication. This paper introduces the Bipartible architecture pattern to optimize cloud-native workload traffic in HPC environments. This paper focuses on optimizing HTTP storage service requests. These requests are transparently transformed onto IB traffic without modifying workload implementation or network configuration. This is achieved by 'cloning' a global HTTP service (BPService) onto the HPC cluster compute host(s) where the workload executes at scale. Provided the global persistent storage is on the IB network the HTTP service requests are returned to the workload via IB and not TCP/IP. The feasibility of this pattern is demonstrated by implementing a prototype BPService for S3 and a Hybrid-BPService (service metadata is accessed over TCP, bulk data over IB) for a software repository service. We offer this pattern in addition to many alternative approaches to address the performance challenges of executing workloads written to cloud-native design patterns in HPC environments. Finally, while the initial results are encuraging signficant validation of any service must be performed under both read and write scenarios before deployment into production is planned.

作者备注:Presented at 8th International Workshop on Containers and New Orchestration Paradigms for Isolated Environments in HPC

AI 论文解读

基于摘要 · 非全文审阅

此版本尚未生成 AI 解读。解读由后台任务生成并按论文版本保存,登录后共享已有结果。

版本差异

目前只收录了一个版本。收录下一版后,可以对照标题、作者、分类和摘要。

观测到的版本

相邻记录可能跳过中间版本;首次发现 v2 及以上也会标为版本更新。

v1 · 2026-11-17 01:30 · 最新观测版本

The Bipartible Architecture Pattern: Transparently Directing HTTP Requests over InfiniBand

Large-scale compute (HPC) systems with coherent-memory workloads often deploy InfiniBand (IB) networks for high-bandwidth and low-latency inter-node and storage communication. A separate TCP network is typically used for control-plane and general-purpose communication. The last decade has seen the rise of cloud-native software patterns. These patterns are characterized by container-based software distribution and inter-node and storage communication over TCP/IP. In an unoptimized HPC environment, a cloud-native workload will typically use HTTP for some or all communication. This paper introduces the Bipartible architecture pattern to optimize cloud-native workload traffic in HPC environments. This paper focuses on optimizing HTTP storage service requests. These requests are transparently transformed onto IB traffic without modifying workload implementation or network configuration. This is achieved by 'cloning' a global HTTP service (BPService) onto the HPC cluster compute host(s) where the workload executes at scale. Provided the global persistent storage is on the IB network the HTTP service requests are returned to the workload via IB and not TCP/IP. The feasibility of this pattern is demonstrated by implementing a prototype BPService for S3 and a Hybrid-BPService (service metadata is accessed over TCP, bulk data over IB) for a software repository service. We offer this pattern in addition to many alternative approaches to address the performance challenges of executing workloads written to cloud-native design patterns in HPC environments. Finally, while the initial results are encuraging signficant validation of any service must be performed under both read and write scenarios before deployment into production is planned.

查看此版本解读 →查看此版本原文 ↗