(Please see the following story on how to Optimise for Docker for Mac). We run a shared file system so changed files can be pushed to git using the host credentials. Presumably this is due to the file sharing system between the docker container and the host machine - Docker for Mac / Mac OS have still got a long way to go here. The tests showed that using Docker for Mac for development is a rather poor (read terrible) experience. Machine 3 is a more powerful Thinkpad X1E I7 8750H 32G Ram. Machines 1 and 2 are recent MacBook Pros: 2.6 GHz Intel Core i7 with 16G Ram. Mac - VM - Linux - Docker ║ 0m6.1s ║ 0m56 ║ The second test included the same change but running the full test suite. The change induced was a config change which involves a recompile (87 files), and we initiated the test framework. We run a single test, and the entire test suite, across an Elixir service. Here we compare the performance of various machine setups. With Docker becoming a standardised toolset for developing and running services locally, it is important that it does not add additional overhead in cycle time. ![]() Developers can maintain focus and not get distracted by pausing and waiting for things to finish. Reducing developer cycle time between a code change and running a test case is hugely important for an effective working environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |