Welcome Guest. Please Login or Register  


You are here: Index > Virtualizor - Virtual Server Control Panel > General Support > Topic : Best Config KVM, Benchmark Disk Speed



Threaded Mode | Print  

 Best Config KVM, Benchmark Disk Speed, to have the fastest and most stable configuration on KVM (1 Replies, Read 9113 times)
lsn_ro
Group: Member
Post Group: Newbie
Posts: 4
Status:
Hi,

Code
$ for x in $(seq 1 10); do echo $x $(dd if=/dev/zero of=test_data.bin oflag=dsync conv=fdatasync bs=104857600 count=1 2>&1 | grep --only-matching -E "[0-9]+\.?[0-9]+ [kKmMgGtT]B/s"); done | tee test_data_write_times.txt


Results:
1 77.2 MB/s
2 78.4 MB/s
3 82.3 MB/s
4 74.2 MB/s
5 81.0 MB/s
6 109 MB/s
7 105 MB/s
8 83.6 MB/s
9 82.4 MB/s
10 93.6 MB/s

The test was done with disk settings:
<disk type='block' device='disk'>
      <driver name='qemu' cache='writeback' io='native'/>
      <source dev='/dev/vg_vms/vs1008'/>
      <target dev='vda'  bus='virtio' />
    </disk>


The same test using the config:
<disk type='block' device='disk'>
      <driver name='qemu' cache='default' />
      <source dev='/dev/vg_vms/vs1008'/>
      <target dev='hda'  bus='ide' />
    </disk>

Results:
1 13.3 MB/s
2 33.3 MB/s
3 29.1 MB/s
4 26.7 MB/s
5 35.0 MB/s
6 7.2 MB/s
7 22.5 MB/s
8 30.8 MB/s
9 37.2 MB/s
10 35.7 MB/s

Dear Virtualizor team which is the fastest and safest configuration to use in production?

L.S.N.
IP: --   

Best Config KVM, Benchmark Disk Speed
siddhesh
Group: Member
Post Group: Newbie
Posts: 30
Status:
Hi ,

Sir we recommend it to use default Caching if the server is production server  .

default is the caching used by default by the kvm .

Writethrough caching means that the host
page cache will be used to read and write data but write notification will
be sent to the guest only when the data    has been reported as written by the
storage subsystem.

Writeback
caching will report data writes as completed as soon as
the data is present in the host page cache.  This is safe as long as you trust your host.
If your host crashes or loses power, then the guest may experience data corruption.

The host page cache can be avoided entirely with <code>cache='none'</code>.
This will attempt to do disk IO directly to the guests memory.

Edited by siddhesh : January 20, 2014, 5:35 am
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is May 26, 2024, 2:12 pm.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 10  |  Page Created In:0.039