** Description changed: [Impact] Using deadline causes performance regressions in Baloo. See bug 1310402 for an example. [Test Case] + * Use Kubuntu trusty until it slows to a crawl * Upgrade kubuntu-settings * Reboot * Make sure boot completes successfully * Make sure IO scheduler is set to CFQ on boot in case you have a HDD : cat /sys/block/sd*/queue/scheduler + * use it and verify it no longer slow to a crawl - [Regression Potential] + [Test Case for Unity] + - installing an Ubuntu precise desktop with unity7 (which I believe was the + last release using cfq by default) and the .0 kernel (3.2.0) + - using the system for a bit to try to reproduce the original problem - + application windows becoming grayed out by the WM under normal usage, + indicating that the app is not responding + - changing the scheduler to deadline and testing to see if the problem + persists or resolves itself + - upgrading to the trusty backport kernel (linux-image-generic-lts-trusty) + - verifying that the desktop behaves correctly with the default deadline + scheduler + - changing the scheduler to cfq and testing whether the original problem + recurs + + + [Regression Potential] None that I can think of, deployment has been successful on Utopic
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378789 Title: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1378789/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
