containers / containers/toolbox

Toolbox containers inflict significant network performance impact on network perf

Open
#1,547 1 comment 0 reactions 0 assignees View on GitHub
1. Bug
Dominant language
Go
Stars
3.5k
Forks
262
Avg merge
3d 1h
Merged PRs (30d)
1

Description

**Describe the bug**

I noticed severe network penalty using the default network/tap setup instatiated for toolbox containers On a 10Gbit connection to a NAS with 20G of bandwidth available to the fabric I am seeing toolbox throughput top out at around 3.5Gbit/s

Rootful distrobox of the same container runs close to line/host kernel rate

**Steps how to reproduce the behaviour**
*Create a toolbox container using fedora:latest tag - install iperf3 or similar tool
*Run iperf3 or similar on a target connected host OS which is able to saturate fabric
*run test from inside toolbox container to target
*repeat for distrobox/rootful container of same image
*repeat from host network userspace

**Expected behaviour**
Throughput should be roughly analogous for all three scenarios

**Actual behaviour**
toolbox containers top out around 3.5gbit

**Screenshots**
Attached
![image](https://github.com/user-attachments/assets/ebface90-0e06-4ea6-8522-637968578ab6)

**Output of `toolbox --version` (v0.0.90+)**
toolbox version 0.0.99.5

**Toolbx package info (`rpm -q toolbox`)**
toolbox-0.0.99.5-11.fc40.x86_64

**Output of `podman version`**

```
Client: Podman Engine
Version: 5.2.2
API Version: 5.2.2
Go Version: go1.22.6
Built: Wed Aug 21 12:00:00 2024
OS/Arch: linux/amd64
```

**Podman package info (`rpm -q podman`)**
e.g., `podman-1.9.2-1.fc32.x86_64`

**Info about your OS**
Fedora40, Nobara, Bazzite(ublue/kiinote)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.