Live data from Hacker News

How does Docker affect energy consumption?

arxiv.org

71–80 of 88 posts

Re: How does Docker affect energy consumption?

#73
post #25

Earlier quoted context omitted.

Does it matter? If one were to find out that it uses more energy because of those components, would that change anything regarding the decision of using it or not because of that higher energy usage?

It matters that you're measuring equivalent things. If systemd replaces three components, you need to compare its energy consumption with those three components, not just with sysv/upstart.

Exactly, the sum of what I need (init + logging + ntp) should be close to using just systemd.

Re: How does Docker affect energy consumption?

#75
post #37
post #34

Doesn't this article fail to consider the bigger, practical picture, i.e. overall resource efficiency/footprint in multi-component architectures? Containers allow us to condense workloads in a single OS runtime –while preserving isolation– where otherwise the same workloads would have spanned multiple machines or VMs, each with its overhead and slack (unused resources). Example: consider you need to deploy not just a…

> Containers allow us to condense workloads in a single OS runtime –while preserving isolation– where otherwise the same workloads would have spanned multiple machines or VMs, each with its overhead and slack (unused resources). I'm starting to believe that the increased density provided by containerization is a myth, in practice. Both because orchestration tools bring their own overhead (compare all the proxies and…

It really do seem like we can't win. Try to get more control in one place, and things sprawl out of control somewhere else.

containers bundled up libs and binaries in a single package, only for an "app" to come reliant on a zoo of containers doing one little part of the whole.

Makes one wonder if the stack is made of rabbits rather than turtles...

Re: How does Docker affect energy consumption?

#76
The article mentions that most of the increased energy consumption was due to the performance of I/O system calls. This was a bit surprising to me since Docker shouldn't have much of an impact of I/O system calls unless you're writing to the container's filesystem, which is copy-on-write. The only reason you should be writing to this filesystem is if you want to incorporate the data you're using into a later Docker image. For high I/O tests like the ones they're doing you should use volumes. Unfortunately I didn't see the actual `docker run` invocations they used to run the tests so I can't know for sure if this was what they were doing. It's just a suspicion.

Re: How does Docker affect energy consumption?

#77

Earlier quoted context omitted.

Great - you've made a hypothesis using your intuition. It seems like it's probably true. The science part is then checking that this it actually is, rather than just assuming, which is what this paper is.

No hypothesis or intuition at play. I've read some of the many articles covering the performance impact of using docker on various metrics. Useful metrics, unlike an electric bill.

Huh? Electric bill is the #1 useful metric for any workload at scale. If you're small, maybe human administration costs dominate that, but otherwise it's virtually guaranteed to be the primary operating cost.

Re: How does Docker affect energy consumption?

#78

Earlier quoted context omitted.

No hypothesis or intuition at play. I've read some of the many articles covering the performance impact of using docker on various metrics. Useful metrics, unlike an electric bill.

Huh? Electric bill is the #1 useful metric for any workload at scale. If you're small, maybe human administration costs dominate that, but otherwise it's virtually guaranteed to be the primary operating cost.

I guess so, but if it matters that means you have hardware and I hate having to manage hardware. So I guess that colors my opinion on the matter.

Re: How does Docker affect energy consumption?

#79

The article mentions that most of the increased energy consumption was due to the performance of I/O system calls. This was a bit surprising to me since Docker shouldn't have much of an impact of I/O system calls unless you're writing to the container's filesystem, which is copy-on-write. The only reason you should be writing to this filesystem is if you want to incorporate the data you're using into a later Docker i…

Wouldn't the copy-on-write nature of the filesystem mean that reads are going to be more heavily impacted?
Post reply on HN