>> Are you talking about building Docker containers on the fly?
>
> I’m a bit baffled what gave you that idea after I’ve spent days arguing for
> strict build/runtime separation?
>
> I was just trying to figure out where you were having this problem:
>
> > ZFS and apt-get + lots of files in a deb = omgiwannamurdersomeone
>
> I heard the opposite of what you meant by this comment -- that you were
> deploying apt-gets + debs using docker and the combination had you wanting to
> murder someone.
It was not clear to me you were referring to that line in particular.
Especially because you were talking about Docker and not about debs.
The problem is a long-standing “bug” (scare quotes because it’s more of a
performance regression) in ZFS-on-Linux:
https://github.com/zfsonlinux/zfs/issues/3857
<https://github.com/zfsonlinux/zfs/issues/3857> (I believe there are more
related tickets but I don’t have the time to investigate). It’s related to
excessive sync calls for every single file that accumulate very fast if you put
a virtualenv with many files into a deb. Basically I have to run containers
with Python debs in YOLO mode (sync=False) if I don’t want installs to take
more than a minute while it takes almost no time on ext4 or XFS.
That said, our Docker containers run on ext4 because our Docker daemon runs in
an LXC and you cannot access the pool from within containers (yet, as I’ve
hear). Which makes it run in VFS mode which is even slower (I’ve measured
factor 3x vs overlay2 in our CI) because it means it has to create a physical
copy of each layer.
I suppose we were talking about different things because I don’t quite
understand why you’re upset.
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python