3 ms·
If your test runs are slower by two orders of magnitude then something is going wrong. For example, I've had problems on docker for Mac where accessing lots of
by VBprogrammer 3y ago
If your test runs are slower by two orders of magnitude then something is going wrong.
For example, I've had problems on docker for Mac where accessing lots of (python) files in a volume mount was slow. I had to use some beta setting at the time which was far better (though I had to do a OS upgrade to use it, which also entailed some IT nonsense).
The overheads of docker are there but if it was that bad people wouldn't use it.
- pletnes 3y agoFile IO seems to be the problem. I’m guessing antivirus + virtualization overhead. Don’t see what I can change about that (use linux, sure). Docker is still useful, it’s great for sharing a complicated setup across machines.
- prewett 3y agoIf I recall correctly, NTFS updates a file's access time (or some such) every time anything happens to it, so by default Windows' file I/O is slow. (Antivirus, of course, will not be helping that.) Once upon a time you could disable access time updating in the registry, although I assume if you had those kind of permissions you wouldn't be having this problem.
- ParetoOptimal 3y agoIt is that bad. I use a Linux VM with docker from OSX and coworkers use docker with OSX. Their compiles take 2m, mine take 30s.