Something troubles me about this article. I hope I'm misunderstanding it.
It's stems from the following quotes; knowing this information, why do AeroFS still think Docker is a good fit for their use-case?
> However, after our move to Docker, we noticed a sharp increase of the appliance's memory footprint.
> ...
> We identified several major factors behind these symptoms:
> 1. an increase in the number of running JVMs, as each tomcat servlet was placed into a separate container
> 2. reduced opportunity for the many JVMs to share read-only memory: the JVM itself, all the shared libraries it depends on, and of course the many JARs used by multiple services
> 3. memory isolation could in some cases confuse some sizing heuristics, which lead to larger caches being allocated by some services