ocaml-maint team mailing list archive

[Clint Byrum <clint@xxxxxxxxxx>]

Wow this is a really old bug report. Still a pretty good idea. :)

I've forwarded this to Debian, marking it as also affects Debian, and
setting status to Triaged. Setting Importance to Wishlist.

** Changed in: approx (Ubuntu)
       Status: New => Triaged

** Bug watch added: Debian Bug tracker #611370
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611370

** Also affects: approx (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611370
   Importance: Unknown
       Status: Unknown

** Summary changed:

- [edgy] Please make gc_approx cron job run nice 19
+ Please make gc_approx cron job run nice 19

-- 
You received this bug notification because you are a member of Debian
OCaml Maintainers, which is subscribed to approx in ubuntu.
https://bugs.launchpad.net/bugs/106944

Title:
  Please make gc_approx cron job run nice 19

Status in “approx” package in Ubuntu:
  Triaged
Status in “approx” package in Debian:
  Unknown

Bug description:
  Binary package hint: approx

  The weekly gc_approx cron job can lead to heavy system load.
  There is no good reason for this background process to have equal priority with user processes.
  I was watching a high resolution HDTV show. 
  When the cron job started mythtv could not get enough processor time to decode the video.
  First there were many glitches and then mythtv locked up.
  I was able to recreate the problem by running the cron job from the command line while watching TV.
  After I changed the cron job to run gc_approx as nice -19 mythtv worked much better.
  There were still a few video glitches but things were much better.