As we want to use Docker’s Container technology to help us fast deployment, but how fast it is?

Let’s do a quick count here:

  • Create a brand new Container
  • Start up the Container
  • Enter into its session
  • Remove the Container

Let’s see how it goes:

  1. Create a brand new Container, 2 seconds, not bad, how fast you can create a new VHD disk which contains a OS?

  2. Start up the Container, almost 8 seconds to get a fully boot OS, how fast does your SSD give your an OS from the moment while you press the power button?

  3. Enter to Container’s Session, 6 seconds to get into the Container’s session, which is similar as normal speed to remote manage other computer. But, don’t forget this is a new machine that it’s not joined the domain, so it’s using local authentication…

  4. Stop the Container then remove it. Total 15 seconds.

Generally, it looks pretty good. As long as we prepared the Image well, with docker build file, we will get much better deployment experience I believe. 🙂

Then we might want to know how it goes with Hardware consumption (Mostly it’s memory) compare to the VM.

  • The current VM I’m running is using 795MB Memory.
  • During the creation of a new Container, it increased to 810MB due to Container Service got started.
  • Start creating the 2nd Container, the memory usage didn’t change too much, around 815MB.
  • Startup one of the container, memory usage increased to 930MB, “CExecSvc.exe” started with session ID = 3
  • Startup the 2nd one, memory usage increased to 1GB, about 70MB different from last state, 2nd “CExecSvc.exe” started with session ID = 4
  • Stop all Containers, memory dropped back to 830MB. all “CExecSvc.exe” terminated
  • Remove all Containers, memory didn’t change.

From this basic test, we can see an Container OS initialized with around 100MB memory usage, and it will only increase if it uses more resources.

In order to use Container in the real world, we need to bring network feature in to let it run some applications. 🙂 Will introduce this in the next blog.