Hi Jose,<br><br>Deduplication or dedup for short is usually a function of =
------=_Part_665_15117543.1369732848335 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Theron,=20 Thanks, that's what I thought. So with dedup we save space in the storage a= nd what about performance, will it increase performance? once it will not u= se the same instance twice, is that right? i.e., if I have 2 VM's (let's sa= y, Fedora 18), with the same kernel, does oVirt run 2 times the 2 instances= or can it manage that so it will not have to run the same software twice, = in order to save resources and performance.=20 I'm not sure if my English is enough for you to realize what I'm trying to = explain.=20 Regards=20 Jose=20 ----- Original Message ----- From: "Theron Conrey" <tconrey@redhat.com>=20 To: suporte@logicworks.pt=20 Cc: Users@ovirt.org=20 Sent: S=C3=A1bado, 25 de Maio de 2013 21:00:39=20 Subject: Re: [Users] deduplication=20 Hi Jose,=20 Deduplication or dedup for short is usually a function of the storage appli= ance, and as such is a "post-allocation" operation. As a quick example the = hypervisor will request the space, allocate all of it, and if space can be = reclaimed via a storage side operation like dedup, that's where it's handle= d.=20 If you're leveraging oVirt with storage appliance that supports dedup it wi= ll work just fine with oVirt as well.=20 We DO however support thin provisioning. This is a "pre-allocation" operati= on handled by oVirt. Instead of just waiting on the storage to reclaim spac= e via a dedup job (if this isn't done inline dedup can be taxing on the sto= rage array and is usually a scheduled job that isn't constant) thin provisi= oning only allocates the storage space that is actually required.=20 More information can be found on our wiki here: http://www.ovirt.org/Vdsm_D= isk_Images=20 Theron Conrey=20 Open Source and Standards, Red Hat=20 @theronconrey=20 ----- Original Message -----=20 From: suporte@logicworks.pt=20 To: Users@ovirt.org=20 Sent: Saturday, May 25, 2013 9:02:40 AM=20 Subject: [Users] deduplication=20 is deduplication possible?=20 Regards=20 Jose=20 --=20 Jose Ferradeira=20 http://www.logicworks.pt=20 _______________________________________________=20 Users mailing list=20 Users@ovirt.org=20 http://lists.ovirt.org/mailman/listinfo/users=20 ------=_Part_665_15117543.1369732848335 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><= div style=3D'font-family: arial,helvetica,sans-serif; font-size: 10pt; colo= r: #000000'>Hi Theron,<br><br>Thanks, that's what I thought. So with dedup = we save space in the storage and what about performance, will it increase p= erformance? once it will not use the same instance twice, is that right? i.= e., if I have 2 VM's (let's say, Fedora 18), with the same kernel, does oVi= rt run 2 times the 2 instances or can it manage that so it will not have to= run the same software twice, in order to save resources and performance.<b= r><br>I'm not sure if my English is enough for you to realize what I'm tryi= ng to explain.<br><br>Regards<br>Jose<br><br><hr id=3D"zwchr"><div style=3D= "color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decorat= ion: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>Fr= om: </b>"Theron Conrey" <tconrey@redhat.com><br><b>To: </b>suporte@lo= gicworks.pt<br><b>Cc: </b>Users@ovirt.org<br><b>Sent: </b>S=C3=A1bado, 25 d= e Maio de 2013 21:00:39<br><b>Subject: </b>Re: [Users] deduplication<br><br= the storage appliance, and as such is a "post-allocation" operation. = As a quick example the hypervisor will request the space, allocate all of i= t, and if space can be reclaimed via a storage side operation like dedup, t= hat's where it's handled. <br><br>If you're leveraging oVirt with sto= rage appliance that supports dedup it will work just fine with oVirt as wel= l. <br><br>We DO however support thin provisioning. This is a "= pre-allocation" operation handled by oVirt. Instead of just waiting o= n the storage to reclaim space via a dedup job (if this isn't done inline d= edup can be taxing on the storage array and is usually a scheduled job that= isn't constant) thin provisioning only allocates the storage space that is= actually required. <br><br>More information can be found on our wiki= here: http://www.ovirt.org/Vdsm_Disk_Images<br><br><br>Theron Conrey<br>Op= en Source and Standards, Red Hat<br>@theronconrey<br><br><br><br>----- Orig= inal Message -----<br>From: suporte@logicworks.pt<br>To: Users@ovirt.org<br=
Sent: Saturday, May 25, 2013 9:02:40 AM<br>Subject: [Users] deduplication<= br><br>is deduplication possible? <br><br>Regards <br>Jose <br><br>-- <br><= br>Jose Ferradeira <br>http://www.logicworks.pt <br><br><br>_______________= ________________________________<br>Users mailing list<br>Users@ovirt.org<b= r>http://lists.ovirt.org/mailman/listinfo/users<br></div><br></div></body><= /html> ------=_Part_665_15117543.1369732848335--