[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-08-26 Thread Thierry Carrez
I agree we should not change the behavior too much now that FeatureFreeze is passed. Adjusting tasks in consequence. ** Changed in: qemu-kvm (Ubuntu Maverick) Status: New = Won't Fix ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = Wishlist ** Changed in: qemu-kvm (Ubuntu)

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-08-25 Thread Thierry Carrez
@Nullzone: that's some very good input, thanks. Looking at your conclusions: ksm is good but need some tweaks to doesnt become a problem more than a help Right, if there is a saner default we should use it, and if there is no sane default we should consider disabling it by default, with strong

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-08-25 Thread Serge Hallyn
Thanks for the info Nullzone! Based on your data, I'm going to spend a bit of time running with: # To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and # sudo restart qemu-kvm KSM_ENABLED=1 #SLEEP_MILLISECS=2000 SLEEP_MILLISECS=50 PAGES_TO_SCAN=100

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-08-18 Thread Nullzone
Hello Thierry, I will try to help showing some information gathered from my lab server as you requested: - Enviroment: 10 x Ubuntu 10.04 x86_64 with several services (SMTP, MySQL, Oracle, DB2, TeamSpeak servers, Tomcats, bind ... etc). 1 x Windows 7 x86_64 3 x Debian Lenny x86_64

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-08-02 Thread Thierry Carrez
17% sounds a bit strong... I'd very much like to see a memory gain / CPU usage chart for various values, or more discussion around the acceptable value upstream. Any idea what the other qemu-kvm distributions are using as a default ? ** Also affects: qemu-kvm (Ubuntu Maverick) Importance:

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-07-30 Thread Dave Walker
This does seem to be a valid bug, some serious CPU time is being dedicated to ksmd. Whilst I haven't seen it in Lucid, i have experienced it in Maverick. Smoser witnessed ~17% CPU utilization for ksmd. Nominating for Maverick. -- Lucid qemu-kvm: ksmd default config is CPU hog

Re: [Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-07-27 Thread Dustin Kirkland
As stated above, I personally don't plan on fixing it in Ubuntu. You can set that value to whatever you want in the config file. Dustin -- Lucid qemu-kvm: ksmd default config is CPU hog https://bugs.launchpad.net/bugs/578930 You received this bug notification because you are a member of Ubuntu

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-07-24 Thread Andy
Is this going to be fixed? -- Lucid qemu-kvm: ksmd default config is CPU hog https://bugs.launchpad.net/bugs/578930 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-07-10 Thread MNLipp
I don't think Won't Fix is appropriate. If you look at at kernel/Documentation/vm/ksm.txt you find that the values for pages_to_scan and sleep_millisecs are documentated as chosen for demonstration purposes. So upstream obviously does not consider these values appropriate for normal operation.

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-07-09 Thread infogerance (Rakotomandimby Mihamina)
See also https://bugzilla.redhat.com/show_bug.cgi?id=541230 ** Bug watch added: Red Hat Bugzilla #541230 https://bugzilla.redhat.com/show_bug.cgi?id=541230 -- Lucid qemu-kvm: ksmd default config is CPU hog https://bugs.launchpad.net/bugs/578930 You received this bug notification because you

[Bug 578930] Re: Lucid qemu-kvm: ksmd default config is CPU hog

2010-05-12 Thread Dustin Kirkland
Hi there- You can actually set it to whatever you want, and have it persist across boots. Just modify the values in the file /etc/default/qemu-kvm. We're just using the default, upstream kernel value for SLEEP_MILLISECONDS, which is 20. It does seem a bit aggressive, but it's the upstream