Updating status for vivid tentatively, until the kernel team can
comment.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1420544
Title:
[SRU] Ubuntu instances on GCE should use NOOP scheduler
Status in linux package in Ubuntu:
New
Status in systemd package in Ubuntu:
Won't Fix
Status in systemd source package in Trusty:
Fix Committed
Bug description:
[IMPACT] By default, the Ubuntu kernel uses deadline. Google has
identified that Cloud Workloads running on Ubuntu perform better using
NOOP as the default scheduler. Google has requested that Google Cloud
Compute (GCE) instances use NOOP as the default.
[FIX] Add udev rule for GCE devices to use NOOP by default.
[VALIDATION]
1. Boot Ubuntu instance on Google GCE
2. Confirm that the scheduler is deadline:
$ cat /sys/block/sda/queue/scheduler
noop [deadline] cfq
3. Install proposed udev package
4. Reboot
5. Confirm that schedule is now noop
$ cat /sys/block/sda/queue/scheduler
[noop] deadline cfq
[RISK] This patch will affect currently running instances and on
reboot they should see better performance. However, there is a risk
that some users will experience a performance hit.
[ORIGINAL REPORT]
Per Google's request, Ubuntu instances should use NOOP as the default
scheduler.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420544/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
