OpenVZ Forum


Home » Mailing lists » Users » Heavy Disk IO from a single VM can block the other VMs on the same host
Re: Heavy Disk IO from a single VM can block the other VMs on the same host [message #44341 is a reply to message #44339] Thu, 01 December 2011 17:27 Go to previous messageGo to previous message
Kirill Korotaev is currently offline  Kirill Korotaev
Messages: 137
Registered: January 2006
Senior Member
That's most likely due to a single file system used for containers - journal becomes a bottleneck.
fsync forces journal flushes and other workloads begin to wait for journal... In reality workload looks like this are typical for
heavy loaded databases or mail systems only.

How to improve:
- increase journal size
- split file systems, i.e. run each container from it's own file system

Thanks,
Kirill


On Nov 29, 2011, at 20:13 , Hubert Krause wrote:

> Hello,
>
> my environment is a Debian squeeze host with a few debian squeeze
> guests. The private and root filesystems of the guest are locatet on
> the same raid device (raid5) in an luksCrypt Container in an LVM
> container on an ext4 partition with nodelalloc as mountoption. If I run
> the tool stress:
>
> stress --io 5 --hdd 5 --timeout 60s (which means fork 5 threads doing
> read/write access and 5 threads doing constantly fsync) the
> responsivness of the other VMs is very bad. That means, Isolation for
> IO operations is not given. I've tried to reduce the impact of the
> VM with 'vzctl set VID --ioprio=0'. There was only a
> minor effect, my application on the other VM where still not
> responsive.
>
> Any Idea how to prevent a single VM to disturb the other VMs regarding
> diskIO?
>
> Greetings
>
> Hubert
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: OpenVZ Container with a PCI ISDN Card
Next Topic: OS/app in the OpenVZ container
Goto Forum:
  


Current Time: Sat Aug 16 10:12:47 GMT 2025

Total time taken to generate the page: 0.19368 seconds