Live data from Hacker News

Another reason why Docker containers may be slow

hackernoon.com

21–30 of 72 posts

Re: Another reason why Docker containers may be slow

#21
post #15

Better title: “nother reason why my code is slow and I’m logging too much”

The point was not to complain about how bad the Docker is but rather to highlight that a lot of unexpected things may come from the fact that the kernel is shared. "Logging too much" was just a reason for the posix_fadvise being called too often but this becomes a problem ONLY when the kernel is shared. In case of virtualization, everyone gets its own version of fadvise (the kernel) and the conflict doesn't happen.

Re: Another reason why Docker containers may be slow

#22
post #2

I don't understand why more people don't use Solaris Zones, they seem to me to be the superior solution by far, and with work done by Joyent you now have modern LX-branded zones also. Is the lack of adoption mainly due to the fact that it's Solaris, and not Linux? (Solaris lives on in Illumos et al)

And deploy it...where? AWS, Azure, GCP and virtually all other providers have first class Docker and Kubernetes support. You can barely even host a Solaris VM anywhere today.

Re: Another reason why Docker containers may be slow

#23
post #22
post #2

I don't understand why more people don't use Solaris Zones, they seem to me to be the superior solution by far, and with work done by Joyent you now have modern LX-branded zones also. Is the lack of adoption mainly due to the fact that it's Solaris, and not Linux? (Solaris lives on in Illumos et al)

And deploy it...where? AWS, Azure, GCP and virtually all other providers have first class Docker and Kubernetes support. You can barely even host a Solaris VM anywhere today.

That would by Joyent [0] the makers of SmartOS (Basically, Open Source Solaris). Their Triton cloud product uses SmartOS under the hood.

[0] - https://www.joyent.com/smartos

Re: Another reason why Docker containers may be slow

#24

Earlier quoted context omitted.

This will help you get similar fs performance in d4mac without falling back to NFS: https://docs.docker.com/docker-for-mac/osxfs-caching/#tuning...

i never tried this but i think it's similar to docker-sync, where you still have to modify your docker compose files. it's not good for people who want a single consistent docker-compose file that would work across varying distributions (ie; opensource project).

:delegated and :cached are ignored on non-MacOS hosts.

Re: Another reason why Docker containers may be slow

#25

Earlier quoted context omitted.

Solaris is not free software and the free software forks never gained much traction. Plus it is now also associated with Oracle which brings along a lot of extra distrust, particularly given how litigious they are.

Illumos/SmartOS is FOSS

Not entirely FOSS. Looks like you need some binaries to actually build it. https://wiki.illumos.org/display/illumos/How+To+Build+illumo...

Re: Another reason why Docker containers may be slow

#26
post #9

Earlier quoted context omitted.

docker-sync ( http://docker-sync.io/ ) is another option that helps resolve filesystem issues on macOS.

i had high hopes for this when i first heard about it but it's no good for me as it requires you to modify your docker-compose file to suit it's needs

you can layer compose configs and put the sync stuff in its own file: `docker-compose up -f docker-compose.yml -f docker-compose-sync.yml`

Re: Another reason why Docker containers may be slow

#27
post #2

I don't understand why more people don't use Solaris Zones, they seem to me to be the superior solution by far, and with work done by Joyent you now have modern LX-branded zones also. Is the lack of adoption mainly due to the fact that it's Solaris, and not Linux? (Solaris lives on in Illumos et al)

> Is the lack of adoption mainly due to the fact that it's Solaris, and not Linux?

I am guessing it is to avoid to learn a whole new ecosystem, tools, environments, rules, package system etc. It's just simpler to stick to Linux. But it all depends, let's say if my application on Illumos shows a 60% performance improvement, well I can see spending time learning it and using it as a base. But it would really have to be large benefit to justify switching OSes. Of course how would I even bother benchmarking to start with? I'd probably have to hear other stories or mentions on HN and such...

Re: Another reason why Docker containers may be slow

#29

Earlier quoted context omitted.

i had high hopes for this when i first heard about it but it's no good for me as it requires you to modify your docker-compose file to suit it's needs

you can layer compose configs and put the sync stuff in its own file: `docker-compose up -f docker-compose.yml -f docker-compose-sync.yml`

or you can just go with dinghy and be done with :p

Re: Another reason why Docker containers may be slow

#30
post #5

on osx, i know for a fact Docker for OSX is pretty darn slow due to its way they handle filesystem. but using Dinghy greatly helped sped everything up due to it using nfs. just in case anyone wanted to know.

It can't be worse than the way they handle the filesystem on Windows. I can't even get events (e.g. watching for changes) to work on volumes.

Reading a bunch of small files from a volume is insanely slow from me in windows, so yeah...
Post reply on HN