opencontainers / opencontainers/runc
runc exec is 5x slower than crun exec
Open
Nobody has claimed this yet.
kind/performance
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
root@ubu2004:/home/kir/git/runc/tst# time for ((i=0; i<1000;i++)); do runc exec xx45 true; done
real 0m20.726s
user 0m11.635s
sys 0m14.094s
root@ubu2004:/home/kir/git/runc/tst# time for ((i=0; i<1000;i++)); do crun exec xx4 true; done
real 0m4.802s
user 0m2.634s
sys 0m2.283s
Need to
- figure out why the difference is so high
- eliminate some of the bottlenecks
Contributor guide
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
Reproduce the provided 1,000-iteration timing comparison between runc exec and crun exec on the stated Ubuntu 20.04 setup. Trace the runc exec path to identify the bottlenecks behind the difference, then verify that the measured overhead is reduced without changing the command's behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100