5 ms·

I can't understand why they would add anymore overhead on such a low powered device.

• jjeaff 8y ago
  Ease of setup and reproducibility probably. And docker doesn't add much overhead, especially when running natively on Linux.
• Gigablah 8y ago
  What overhead? "Docker induces no significant overhead on CPU nor memory usage, compared to a native execution (worse observation: -4%; 0% on all others)" [1] [1]: https://roudier.io/2015/08/docker-vs-kvm-vs-native-performance-comparison/ https://roudier.io/2015/08/docker-vs-kvm-vs-native-performan...
  • krageon 8y ago
    Think about how the stack works. I'm not saying this measurement is definitely wrong, but if you're finding exactly 0 overhead then you have to suspect there is something weird going on with how you're measuring it.
    • Gigablah 8y ago
      The processes are still running natively. The most common overheads would be due to network and storage driver and those can be mitigated with some simple settings. The Docker daemon is more or less a process supervisor at this point.
      • krageon 8y ago
        I think we have a fundamentally different view of what "natively" means and what it means to be "more or less a process supervisor". That's fine, but it also means we won't get to an agreement that we are both at peace with in this case.
        • tinco 8y ago
          What feature of Docker makes you consider it significantly more than a process supervisor?
• viraptor 8y ago
  Zero and original raspberries can be low-powered. 3+ is a quad core with 1gb memory. Docker doesn't even show up on CPU monitor and takes 2% shared memory in my case. The overhead of a namespace is not really noticeable either, unless you're doing lots of processing. (My influx+grafana+monitors sit under 5% CPU almost all the time)