[Users] Ploop Random I/O

Devon B. devon.b at virtualcomplete.com
Tue Sep 30 08:31:32 PDT 2014


You should read more of the resources available at openvz.org: 
http://openvz.org/Ploop/Getting_started#Resizing_a_ploop_image

There are no specific inode settings for ploop, it creates a private 
ext4 filesystem for each container, therefore the inode limit is only 
dependent on the filesystem (ext4).

On 9/30/2014 10:49 AM, Matt wrote:
> In ploop, can inodes and disk size easily be increased for a container?
>
> On Wed, Sep 24, 2014 at 7:34 PM, Kir Kolyshkin <kir at openvz.org> wrote:
>> On 09/19/2014 11:45 AM, Matt wrote:
>>> I have a container currently using about 150GB of space.  It is very
>>> random I/O hungry.  Has many small files.  Will converting it to ploop
>>> hurt I/O performance?
>> In case of many small files it might actually improve the performance.
>>
>> ploop performance is very close to usual FS, except for then the image
>> is growing -- this operation somewhat slows it down as it needs to allocate
>> extra blocks and modify the block address table. I guess it's not an issue
>> in your case.
>>
>> But don't take my word for it, give it a try yourself!
>>
>> Kir.
>> _______________________________________________
>> Users mailing list
>> Users at openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://lists.openvz.org/mailman/listinfo/users



More information about the Users mailing list