|
|
|
|
|
|
by throwaway894345
1902 days ago
|
|
|
We ran into this as well. The I/O would cripple the system. It seems like if you have a compiled language in which the sources are compiled into a single binary that runs on your Docker VM, things are not so bad, but in an interpreted language with the sources on the host’s disk and the interpreter running on the guest, the VM needs to reach across that host/guest VM boundary all the time. We also tried all the tricks to speed it up, but we ultimately gave up and just used native MacOS processes. |
|
|