Killing 1000 containers seems to be slow

Bug #1570940 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Invalid
High
Canonical Server
docker.io (Ubuntu)
Invalid
Low
Canonical Server

Bug Description

== Comment: #0 - Thorsten Winkler - 2016-04-11 11:48:33 ==
Hi

to reproduce this I only started 1000 containers using:
     - docker run --name "sleep_$i" -d image_name sleep 100000

After that I tried to kill them in a for-loop with:
     - time docker kill sleep_$i

At the beginning of killing 1000 containers (see attachment) it takes on average about ~0.7/0.8 seconds to kill one container which seems for me a bit too slow. Maybe someone can have a look at this please?

#------------------------------------------------------------------------------------------------------------------------
Used system / system infos:
- 10GB Memory
- 4 CPUs

#docker version
Client:
 Version: 1.10.2
 API version: 1.22
 Go version: go1.6
 Git commit: c3959b1
 Built: Sun 13 Mar 2016 22:50:51 100
 OS/Arch: linux/s390x

Server:
 Version: 1.10.2
 API version: 1.22
 Go version: go1.6
 Git commit: c3959b1
 Built: Sun 13 Mar 2016 22:50:51 100
 OS/Arch: linux/s390x

#docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.10.2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 2
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file docker ve
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.0-12-generic
Operating System: Ubuntu 16.04
OSType: linux
Architecture: s390x
CPUs: 16
Total Memory: 9.812 GiB
Name: s83lp36
ID: NV7U:5PTO:RDKL:JGJ2:OYXO:4VU6:THQQ:M5IS:FKDL:E5ZF:OBUZ:IELL

== Comment: #5 - Heinz-Werner Seeck - 2016-04-15 03:05:04 ==
The expected performance goal is around 0.4 seconds.

Revision history for this message
bugproxy (bugproxy) wrote : Diagram: AVG time to kill a container

Default Comment by Bridge

tags: added: architecture-s39064 bugnameltc-140208 severity-high targetmilestone-inin1610
Changed in ubuntu:
assignee: nobody → Skipper Bug Screeners (skipper-screen-team)
Kevin W. Rudd (kevinr)
affects: ubuntu → docker (Ubuntu)
dann frazier (dannf)
Changed in docker (Ubuntu):
assignee: Skipper Bug Screeners (skipper-screen-team) → Canonical Server Team (canonical-server)
Changed in ubuntu-z-systems:
assignee: nobody → Canonical Server Team (canonical-server)
Changed in docker (Ubuntu):
importance: Undecided → Low
Changed in ubuntu-z-systems:
importance: Undecided → High
affects: docker (Ubuntu) → docker.io (Ubuntu)
Revision history for this message
Jon Grimm (jgrimm) wrote : Re: [Ubuntu16.04] Killing 1000 containers seems to be slow

>>The expected performance goal is around 0.4 seconds.

What is this expectation based on?

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-04-18 09:58 EDT-------
Our expectation is based on our performance work so far (with other distributions but also using upstream kernel and Docker).

We have noted http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3d93116cef306bd516a7645e7b4895d1d0ceec2b and http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=728dba3a39c66b3d8ac889ddbe38b5b1c264aec3 made a difference, but these patches should be in Ubuntu 16.04 already, so we are not sure where the difference comes from.

bugproxy (bugproxy)
tags: added: targetmilestone-inin16041
removed: targetmilestone-inin1610
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Triaged
summary: - [Ubuntu16.04] Killing 1000 containers seems to be slow
+ Killing 1000 containers seems to be slow
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2016-08-10 08:59 EDT-------
I tested it now again and all tests based on the same system with 8 CPUs and 10 GB of memory!
All references and comparable systems now have similar and acceptable results.
So based on a this new investigation it looks good for me and this bug can be closed.

Revision history for this message
Jon Grimm (jgrimm) wrote :

Thanks, I'll just mark invalid to close out.

Changed in ubuntu-z-systems:
status: Triaged → Invalid
Changed in docker.io (Ubuntu):
status: New → Incomplete
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.