It would also be worth checking if you have a mismatch (or misalignment) on
block size. If the disk is 4k physical, and you have an ashift=9 pool,
you'll lose even more iops to internal rmw cycles.
On Wed., 28 Mar. 2018, 07:10 Ian Collins, wrote:
> On 03/28/2018 09:04
On 03/28/2018 09:04 AM, Jeremy wrote:
The disk is now very fast, only 5400 rpm. I have not done any tests
yet. I was running hyper-v on the same system with much faster
performance, but I suspect these are probably not comparable.
In SmartOS, KVM writes are synchronous, so performance will
typo: Not* very fast
On Tue, Mar 27, 2018 at 4:04 PM, Jeremy wrote:
> The disk is now very fast, only 5400 rpm. I have not done any tests yet. I
> was running hyper-v on the same system with much faster performance, but I
> suspect these are probably not comparable.
>
> On
The disk is now very fast, only 5400 rpm. I have not done any tests yet. I
was running hyper-v on the same system with much faster performance, but I
suspect these are probably not comparable.
On Tue, Mar 27, 2018 at 3:07 PM, Greg Treantos wrote:
> how fast is your disk? Did
how fast is your disk? Did you do any perf testing under other op-systems?
I usually will boot a live version of linux and run some basic perf tests.
In the newer versions they include a disk test that seems OK. Or you can
use something like bonnie++
On Tue, Mar 27, 2018 at 2:58 PM, Jeremy
I am building a small testing box, just to try out images and to only run
one or maybe two VMs at a time.
The trouble is, it only has one drive. So any file system operation in the
VM seems to take forever.
Is there any way to speed this up? Is is this a limitation of running ZFS
on a single