From: Daniel Poelzleithner <poelzi@poelzi.org>
To: linux-kernel@vger.kernel.org
Subject: [ANN] ulatencyd 0.3.1
Date: Tue, 18 Jan 2011 11:57:08 +0100 [thread overview]
Message-ID: <4D357204.3090505@poelzi.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]
Hi all,
I'm happy to announce the release of ulatencyd 0.3.1
What is it ?
============
ulatencyd is a scriptable daemon which constantly optimises the Linux
kernel for best user experience.
The default configuration tries reduce the latency for a typical desktop
system and protects the system from malicious processes/groups.
With a different configuration all other types of systems can be
adjusted as well.
Website: <https://github.com/poelzi/ulatencyd/>
• Ubuntu PPA: <https://launchpad.net/~poelzi/+archive/ulatencyd-stable>
• Latest Release:
<https://github.com/downloads/poelzi/ulatencyd/ulatencyd-0.3.1.tar.gz>
What's new in 0.3 (very short version)?
=======================================
• X-Server plugin which monitors the active windows and gives more
priority to the recently active windows.
• Full scripted scheduler with flexible configuration that allows easy
adjustment of the resulting cgroups and parameters.
• Protection rules against common cases of memory shortage, also known
as the swap of death (even without swap).
• Scheduler configuration for desktop systems
• Fast C core with Lua embedding. Intelligent caching to reduce the
load on filter rules and scheduler.
• Very detailed API for system inspection and adjustment.
• Rudimentary Rules for popular Desktop Environments KDE & Gnome
Does it work ?
==============
Yes. Of course it is possible to still cause a swap of death or overload
the system so much, that it starts to get lag. But typical cases get
caught by the current rules. A make -j 50 of the linux kernel
on my dual core machine with 4 GB ram let me still work on the machine
quite well, but a make -j 80 still locks it down for like 4 minutes.
This is most likely because the heavy swapping done on the isolation
groups (their main memory usage is restraint). This may be fixed by
using the blockio subsystem, but this is not used yet. Planned for the
next version.
kind regards
Daniel Poelzleithner
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next reply other threads:[~2011-01-18 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 10:57 Daniel Poelzleithner [this message]
2011-01-18 13:03 ` [ANN] ulatencyd 0.3.1 Vasiliy G Tolstov
2011-01-18 15:32 ` Frederik Himpe
2011-01-18 15:59 ` Vasiliy G Tolstov
2011-01-18 16:36 ` Vasiliy G Tolstov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D357204.3090505@poelzi.org \
--to=poelzi@poelzi.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.