3 ms·

At GitLab all team members develop without virtualization. Disk IO is just much faster that way. We recommend the approach in our development kit https://gitlab

by sytse 10y ago

At GitLab all team members develop without virtualization. Disk IO is just much faster that way. We recommend the approach in our development kit https://gitlab.com/gitlab-org/gitlab-development-kit https://gitlab.com/gitlab-org/gitlab-development-kit We would love to see better virtualization disk performance so it is easier for non-team members to contribute. We're happy that despite that people are still able to contribute https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope=all&state=opened&utf8=%E2%9C%93&label_name%5B%5D=Community+Contribution https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope...

emilburzo 10y ago
That's interesting, but shouldn't containers (e.g.: docker/lxc) be almost as fast as native at disk I/O? I mean that's basically why I moved my self hosted virtual servers from KVM, which was abysmal on regular desktop spinning disks, to LXC/Docker which is comparably fast to native -- plus I can fit a lot more containers than full VMs.
- sytse 10y ago
  The problem is that on MacOS you have to run containers in a virtual machine since you're not running on Linux. Crossing the VM boundary with IO can be slow, especially on virtualbox.
  - emilburzo 10y ago
    Oh, I'm not using MacOS so I didn't know that. It makes a lot more sense now, thanks!