We noticed that if one of the instances starts doing a lot of disk I/O, it affects the performance of the other instances on the server. Is Xen supposed to limit one instances effect on another?
On the CPU side Xen can easily limit a process to a single core and hence limit any “resource hogging” on the box, but this is harder when it comes to a disk. If two instances are trying to read from the same disk platter there is a basic “seek” time hit; there is only disk head on the platter and every time it switches to reading for one instances to another it needs to “seek” the location of the new file on the disk. There’s not much that virtualization can do to solve this problem. This is one reason we think it is important to have control over the entire server: so you can avoid resource contention!
Related Questions
- We noticed that if one of the instances starts doing a lot of disk I/O, it affects the performance of the other instances on the server. Is Xen supposed to limit one instances effect on another?
- Can the HP Web Jetadmin SQL 2005 Server instance co-exist with other SQL 2005 Server instances?
- How do I start a single application server instance rather than all the instances in a domain?
