Hello Ben, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.11 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1420544

Title:
  [SRU] Ubuntu instances on GCE should use NOOP scheduler

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
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/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to