3 ms·
You're using Docker Compose on Mac? I tried when it was still called Fig, and while it was wonderful for simplicity, the filesystem performance for VirtualBox/b
by feedjoelpie 11y ago
You're using Docker Compose on Mac? I tried when it was still called Fig, and while it was wonderful for simplicity, the filesystem performance for VirtualBox/boot2docker made it brutal to use. My Rails apps in development mode (therefore serving up many individual assets) would take almost a minute to load each page.
Has it gotten better, is there a trick you're using, or am I hitting an edge case you don't have?
- mmattax 11y agoYeah, the filesystem for VBox got significantly better (use to have to use a custom ISO to get volume shares to work properly). We haven't had a problem since the Docker 1.3 update.
- superuser2 11y ago>would take almost a minute to load each page VirtualBox filesystem performance isn't amazing, but it isn't anywhere near that bad. There was probably another issue involved here.
- feedjoelpie 11y agoI really don't think so. You might just be underestimating the number of static asset files in a client-heavy web app before concat/minify ever happens. Watching the logs, you could see... each... little... file... take... way too long.
- bentruyman 11y agoNo, we ran into the same issues. When dealing with mid-sized Node.js projects in particular where the dependency tree may include something like 70k source files. `npm install` can take several minutes, builds on-save could take several seconds. We resolved to simply doing everything inside of a VM, using sshfs to "persist" the data out to the host machine on-demand for those uncomfortable using vim/tmux inside the VM.