Speed up multidim-interop test runner
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 65
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
In CI (using GitHub runners), each test (starting docker compose until it exits) takes about 2s. It’s unclear why this takes so long. My hunch is that it’s not the actual test that takes a while (the handshake and ping time is around 50-300ms), but the cost to setup the cgroups, network namespaces, and other docker specific things. Running the simplest docker image of hello-world takes around 400ms on my machine (time docker run --rm hello-world). There must be something here we can optimize.
Increasing the number of parallel compose stacks does not help (It does however help a bit on bigger machines).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CI job that launches the Docker Compose stacks and measure container setup separately from the handshake and ping. Compare the cgroups, network namespace, and other Docker setup costs across different runner sizes or execution paths. Done means identifying the dominant delay and demonstrating a faster per-test runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, github-actions
- Domain
- ci-cd, devops, performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100