Jason White <[email protected]> writes: > Carl Turney <[email protected]> wrote: > >> Could any of you point me to instructions to get Ubuntu to limit or >> choke the demand that the Thunderbird process calls upon the CPU? > > This won't help you (but it might be of interest to others): the > Systemd developers have been working on this. In particular, since > every user session or system daemon occupies its own container, it's > possible to limit CPU time and other resources of the appropriate > container [...]
This functionality is available without systemd. At at Ubuntu 10.04, you can limit a container to specific cores and set RAM and swap caps. You cannot set I/O throughput constraints without a newer kernel. It is trivial to set resource constraints on a container. I work with full chroots, but I believe to move a process into a container it is as straightforward as echo $pid >>/dev/cgroup/$container/cgroup.procs. Post-Lucid kernels also have SCHED_AUTOGROUP: │ This option optimizes the scheduler for common desktop workloads by │ automatically creating and populating task groups. This separation │ of workloads isolates aggressive CPU burners (like build jobs) from │ desktop applications. Task group autogeneration is currently based │ upon task session. Prior to that, I recommend investigating nice, ionice and ulimit, but these are probably too coarse-grained for something like tbird. _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
