[pve-devel] KVM Live Backup performance

[Cesar Peschiera]

Thanks for your nice answer Eric

@Dietmar or anyone that can answer, please let me to do a questions:

Note: 
These questions is because I am involved in a project and the idea is to use several RAID 10 in the same PVE Host for use of a VM with MS-SQL Server, and for the backup a single SATA hard drive will be used on an NFS Server, and i don't want get performance degradation or at least a minimun of degradation

1- But as the buffer need RAM free, what are the RAM requirements for use this buffer?
2- The requeriments of buffer RAM will be always static in any case, or will be dinamic?
3- If is dinamic, which will be the formula that i need to know for obtain a nice performance? (for buy the RAM that will be necessary)
4- Will get I at least a minimum of degradation in this case (obviously while "KVM Live Backup" is running)? (see the note above)

Best regards
Cesar
  ----- Original Message ----- 
  From: Eric Blevins 
  To: pve-devel at pve.proxmox.com 
  Sent: Tuesday, January 28, 2014 11:12 AM
  Subject: Re: [pve-devel] KVM Live Backup performance






    Anyways, I will try to upgrade KVM to 1.7 first (many backup related changes). 
    We can then test again and try to optimize further.


  Cesar, from my testing KVM 1.7 fixed the backup related performance issues.
  See archive: http://pve.proxmox.com/pipermail/pve-devel/2013-December/009296.html

  The buffers related to Live backup are for the data sent to the backup, not the data sent to the VMs disk.
  The data sent to the disk will still use whatever cache policy you have set for that disk.



------------------------------------------------------------------------------


  _______________________________________________
  pve-devel mailing list
  pve-devel at pve.proxmox.com
  http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20140128/fd639896/attachment.htm>