Introduction
Introduction Statistics Contact Development Disclaimer Help
Post AimIBwsdHF1zV6ySbw by [email protected]
More posts by [email protected]
Post #AimFdrPKux0wm2tAjA by [email protected]
0 likes, 4 repeats
Proxmox vs FreeBSD: Which Virtualization Host Performs Better?Since migrating m…
Post #AimIBwsdHF1zV6ySbw by [email protected]
0 likes, 0 repeats
@stefano This is interesting. Thanks.The file creation speed is very significan…
Post #AimIV7Tw5Il7spZ1gu by [email protected]
0 likes, 0 repeats
@stefano Thanks,I've recently moved some of my VMs from KVM to bhyve and ha…
Post #AimPsromfmKpvraPJo by [email protected]
0 likes, 0 repeats
@stefano Rule of thumb: if ZFS consistently beats ext4 in a basic filesystem be…
Post #AimXrvaXy6mgyAzRWS by [email protected]
0 likes, 0 repeats
@paul @stefano bhyve sounds great
Post #AimXrveniIBfBMyq9Y by [email protected]
0 likes, 1 repeats
@ben to be fair it's probably ZFS doing a lot of the heavy lifting here, bu…
Post #Aimc4YPFs09AeWz5qy by [email protected]
0 likes, 0 repeats
@stefano ZFS on Linux still not mature yet, and FreeBSD support ZFS out of the …
Post #AimvUan7WWxchwHE4O by [email protected]
0 likes, 0 repeats
@paul @ben @stefano I don’t know, I could equally imagine the Qemu I/O paths …
Post #Ain3ojv45ukYRX6vo0 by [email protected]
0 likes, 1 repeats
@stefanoThis is excelent, thanks for sharing it. One other test that might be …
Post #AinGuZrXhHVwOUZqQS by [email protected]
0 likes, 0 repeats
@stefanoNice article! 💪Are you trying to do the competition to Phoronix? 🤪
Post #AinMBuo3a6ey2m2892 by [email protected]
0 likes, 0 repeats
@stefano Please next time you do benchmarks, use FreeBSD's ministat(1):-)
Post #Aioaql7e5HeSOlWexc by [email protected]
0 likes, 1 repeats
@stefano Very nice detailed comparison. I made the right choice to move to VMs …
You are viewing proxied material from pleroma.anduin.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.