Sluggish desktop when building a virtual disk in VirtualBox OSE on 11.2 M8
I'm not ready to file a bug on this just yet, but I wanted to see if anyone else had run into this. The scenario: 1. Install 11.2 Milestone 8. KDE desktop. Hardware is a 4 GB x86_64 Athlon64 X2 (dual core) 2. Install VirtualBox and start the drivers (/etc/init.d/vboxdrv start) 3. Create a 1 GB virtual machine and allocate a 20 GB fixed-size disk. When the virtual disk creation starts up, the responsiveness of everything else on the desktop suffers. I don't have any hard measurements yet, and I haven't tried this recently with 11.1, but it *seems* like it was a *lot* better on 11.1. So: 1. Has anybody else seen / tried this? 2. If they have, is anyone looking at kernel memory management tuning? 3. How common a scenario is this? I do it all the time, but is it worth modifying the distribution parameters? -- M. Edward (Ed) Borasky http://borasky-research.net "I've always regarded nature as the clothing of God." ~Alan Hovhaness -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org
M. Edward (Ed) Borasky wrote:
I'm not ready to file a bug on this just yet, but I wanted to see if anyone else had run into this. The scenario:
1. Install 11.2 Milestone 8. KDE desktop. Hardware is a 4 GB x86_64 Athlon64 X2 (dual core) 2. Install VirtualBox and start the drivers (/etc/init.d/vboxdrv start) 3. Create a 1 GB virtual machine and allocate a 20 GB fixed-size disk.
When the virtual disk creation starts up, the responsiveness of everything else on the desktop suffers. I don't have any hard measurements yet, and I haven't tried this recently with 11.1, but it *seems* like it was a *lot* better on 11.1. So:
1. Has anybody else seen / tried this? 2. If they have, is anyone looking at kernel memory management tuning? 3. How common a scenario is this? I do it all the time, but is it worth modifying the distribution parameters?
| 1. not exactly this, but dd if=/dev/zero of=z bs=1M also slowed things down a bit here |||| ||2. tuning mm might involve writing values to /proc/sys/vm/dirty_* 3. not killing interactivity is always a good idea, if it does not hurt performance too much. | |This could also be a question of IO-scheduler priorities. You can try adding to your kernel line in /boot/grub/menu.lst elevator=deadline elevator=cfq elevator=as (should be default) and compare your experience. | -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org
participants (2)
-
Bernhard M. Wiedemann
-
M. Edward (Ed) Borasky