touch-packages team mailing list archive

[Adam Conrad <adconrad@xxxxxxx>]

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd source package in Trusty:
  Fix Released

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