Re: [Xen-users] Sparse or non sparse

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

How quickly do you expect to be filling it up, or how much data do you expect 
to write at one time?  If it's slow growth, performance won't be an issue.  If 
you expect to write several hundred GB at a time, it might be better to 
pre-allocate, as you'll see less I/O wait.

-Nick

>>> On 2010/06/02 at 13:46, Paras pradhan <pradhanparas@xxxxxxxxx> wrote: 
> Sorry, I meant to say sparse does not perform better than non sparse.
> 
> Paras.
> 
> 
> On Wed, Jun 2, 2010 at 2:45 PM, Paras pradhan <pradhanparas@xxxxxxxxx>wrote:
> 
>> I am not worried about the space at this moment but worried about the
>> performance. I know non sparse does not perform better than spasre images
>> but don't know how much. Any rough numbers ?
>>
>> Thanks,
>> Paras.
>>
>>
>> On Wed, Jun 2, 2010 at 1:55 PM, Nick Couchman <Nick.Couchman@xxxxxxxxx>wrote:
>>
>>> That depends on how much space is available on the volume/disks that are
>>> storing this file, and how many other domUs are running there.  If there are
>>> many other domUs, or if this comes close to filling up your entire physical
>>> disk/array, this may not be a good idea, because you may overallocate your
>>> disk space and end up filling up the disk.
>>>
>>> -Nick
>>>
>>> >>> On 2010/06/02 at 09:34, Paras pradhan <pradhanparas@xxxxxxxxx> wrote:
>>> > Hi,
>>> >
>>> > Normally I use tap:aio with sparse img files to create a domUs.  I need
>>> to
>>> > add a 1TB image to one domU and expecting that it would be almost 100%
>>> full
>>> > before I extend it to 1.5TB. In this case is it safe to use sparse
>>> files?
>>> >
>>> > Thanks!
>>> > Paras.
>>>
>>>
>>>
>>>
>>> --------
>>> This e-mail may contain confidential and privileged material for the sole
>>> use of the intended recipient.  If this email is not intended for you, or
>>> you are not responsible for the delivery of this message to the intended
>>> recipient, please note that this message may contain SEAKR Engineering
>>> (SEAKR) Privileged/Proprietary Information.  In such a case, you are
>>> strictly prohibited from downloading, photocopying, distributing or
>>> otherwise using this message, its contents or attachments in any way.  If
>>> you have received this message in error, please notify us immediately by
>>> replying to this e-mail and delete the message from your mailbox.
>>>  Information contained in this message that does not relate to the business
>>> of SEAKR is neither endorsed by nor attributable to SEAKR.
>>>
>>
>>




--------
This e-mail may contain confidential and privileged material for the sole use 
of the intended recipient.  If this email is not intended for you, or you are 
not responsible for the delivery of this message to the intended recipient, 
please note that this message may contain SEAKR Engineering (SEAKR) 
Privileged/Proprietary Information.  In such a case, you are strictly 
prohibited from downloading, photocopying, distributing or otherwise using this 
message, its contents or attachments in any way.  If you have received this 
message in error, please notify us immediately by replying to this e-mail and 
delete the message from your mailbox.  Information contained in this message 
that does not relate to the business of SEAKR is neither endorsed by nor 
attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users