4 ms·
It doesn't even take that much. Docker Desktop on MacOS is widely known to be terrible and have extremely poor performance. Running webpack-dev-server with file
by baddox 7y ago
It doesn't even take that much. Docker Desktop on MacOS is widely known to be terrible and have extremely poor performance. Running webpack-dev-server with filewatching through Docker nearly grinds my 2017 Macbook Pro to a halt. Obviously most node/webpack/JS stuff can run natively on Mac but it's not uncommon to see dev stacks that dockerize everything because that's how the production stack works.
- emerongi 7y agoI often have up to 10 VSCode editors, an IntelliJ window and two browser instances open. Add some server processes, UI watchers/builders, and my Thinkpad starts to freeze up. In an ideal world, I would have a low-latency remote desktop going, but even in 2020 it seems like a pipe dream.
- oarsinsync 7y agoI’ve been using paperspace cloud machines with parsec for low latency Remote Desktop. Originally used it for gaming. It’s remarkable how good it is for everything else too. 5ms encoding lag, 10ms network lag, totally workable.
- bdcravens 7y agoYou can improve this substantially on MacOS using docker-sync (the issues with Docker performance on Mac are primarily related to the file system) I wrote a little about this; it's for Rails but the same ideas apply: https://medium.com/@bdcravens/fixing-docker-for-mac-and-rails-performance-baf35f554bc7 https://medium.com/@bdcravens/fixing-docker-for-mac-and-rail...
- baddox 7y agodocker-sync helps a little bit, and so does limiting Docker to 1 CPU core, but I still routinely get spurts 100% CPU from Docker that despite supposedly being on 1 core still grind my machine to a halt.