So don't blame unraid or LT, its a trade-off for a very cheap, highly compatible and very versatile system. HERE is a comparison between bare-metal, vmware and kvm (from 2013). To achieve that, I would recommend IOMETER, you can test all sorts of possible workloads.īut on the other side, 50-70% of bare-metal is basicly what you can expect of kvm (depending of workload). That way its very unlikely to hit any cached data. Otherwise even passthrough would not bypass the caching in the VM, just outside.Ī good start to make sure there is not much caching going on, is to run very long benchmarks (hours) with very large amounts of random data (multiple times the amount of RAM 10GB+). To completly bypass any cache, you would still need to disable caching IN your VM or use software that does not use cache for benchmarks. It was the last cache mode added, completing the possible combinations of caching and direct access semantics. Like cache=writethrough, it is helpful to guests that do not send flushes when needed. This mode causes qemu-kvm to interact with the disk image file or block device with both O_DSYNC and O_DIRECT semantics, where writes are reported as completed only when the data has been committed to the storage device, and when it is also desirable to bypass the host page cache. The hard drive is a Samsung SSD 850 EVO 120GB.ĬrystalDiskMark 5.1.2 圆4 (C) 2007-2016 hiyohiyo
I ran CrystalDiskMark within a Windows 10 VM running on my E3 Xeon TS140.
Not sure how to answer your question more broadly, but happy to provide some data.
0 kommentar(er)
