#virtiofs — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #virtiofs, aggregated by home.social.
-
Файловый сервер SAMBA / pool ZFS
Всегда хотел развернуть шару SMB с хранилищем на ZFS, но есть нюансы… Совершенно не приемлю, чтобы пользователи каким либо образом взаимодействовали с сервером, где расположен pool\ZFS. В моем понимании, СХД может включать в себя только служебные компоненты без прямого пользовательского доступа к его сети. Идея казалось очень простой - поднимаем виртуальный сервер, подключаем его к домену, цепляем туда существующий ZFS пул....
-
Unhappy with #DockerDesktop on #macOS? Give #Colima a try!
It's a free and open #container runtime for macOS. It now supports the macOS #virtualization framework, #virtiofs for fast volume mounts and forwarding #inotify events for hot/live reloading. It can even provide a #containerd, #kubernetes or #incus runtime.
https://github.com/abiosoft/colima
(I would've preferred #podman, as that's what I'm mostly using in production, but it still doesn't support forwarding inotify events on macOS)
-
I've switched from #9pfs to #virtiofs mount for a VM I run under my #proxmox host at home and did a few #fio benchmarks.
9pfs (before):
seq read (1M, 1 thread) - 1950 MiB/s
rand read (4K, 4 threads) - 213 MiB/s
seq write (1M, 1 thread) - 468 MiB/s
rand write (4K, 4 threads) - 80 MiB/svirtiofs (after):
seq read (1M, 1 thread) - 5258 MiB/s
rand read (4K, 4 threads) - 291 MiB/s
seq write (1M, 1 thread) - 1074 MiB/s
rand write (4K, 4 threads) - 84 MiB/s2.7x sequential read, 2.3x sequential write, 1.3x random read, and 1.05x random write.
Pretty good improvements!
Especially that this is for my media (movies/tv) mount where mostly sequential I/O is typically performed.
Note the underlying hardware is Samsung QVO SATA SSD, which is rather slow SSD, and likely a bottleneck in those random read/write tests. I expect there would be much bigger differences on a fast NVMe drive.
