I was trying to separate work from after-work activities by using two operating systems, switching from one to another based on what I wanted to do.

Unfortunately, I had only one computer for work and entertainment, and for this second task, Linux was not good enough for me. I prefer the command line over GUI and also Symfony based projects were quite slow on windows back then. Why not buy a “normal” computer with Linux on it?Īt the very beginning, I was a Windows user and did not need a lot of time to realize that it is not well suited for my programmer career.

For some applications, this won’t be a big problem, but all apps which perform many I/O disk operations will be affected and probably not usable. These are related to volume performance, the way volumes are mounted, and the underlying osxfs filesystem. On Mac has had some performance issues since the beginning. We’ll fire up an Ubuntu container to test.Update for 2022: Docker on new MacBook with M1 Pro Why is Docker on Mac so slow? What about Docker?ĭocker containers are allocated 64 MB of shared memory by default. So we need to ensure that there is shared memory available in a container. Now it stands to reason that if these applications are using shared memory on my desktop then they will probably want to use it in a Docker container too. Some applications (like Firefox) use multiple segments of shared memory. Many desktop applications (for example, Slack, Firefox, RStudio, Thunderbird and DBeaver) use shared memory. If we look up the PIDs this is what we find: 268958 /usr/lib/rstudio/bin/rstudio

Those shared memory segments were created by four distinct processes. The cpid column gives the PID of the process that created the shared memory segment, while the lpid column reflects the PID of the last process which interacted with it.

Memory allocated to docker on mac