Advanced Gtk+ Sequencer - News

Group

Main
- Main
- View members
- Search
Homepage
Download
Docs
Support
- ~~Submit new~~
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
Mailing lists
Source code
Bugs
- Submit new
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
Tasks
- ~~Submit new~~
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
News
- Browse
- Atom feed
- ~~Submit~~
- ~~Manage~~

It's about systemd and performance

Item posted by Joël Krähemann <jkraehemann> on Tue 23 Aug 2016 10:45:49 PM UTC.

Advanced Gtk+ Sequencer v0.7.50

Realtime behavior was much improved and you might experience good throughput. I have adopted Gtk+ main loop and integrated GMainContext in gsequencer. Further we use ppoll() instead of poll(). If you are interested in details you might consider `man poll`.

It seems systemd has a kind of penetrant management to do accounting of ressources. It's not perfect but with the following it works better:

systemd-run -p CPUAccounting=false -p MemoryAccounting=false -p TasksAccounting=false -p IOAccounting=false -p BlockIOAccounting=false --scope gsequencer --filename agsly.xml

Systemd calculates wrong time information and I think that's why accounting seems over-helming. Might be if you do real-time stuff you want to disable it system wide.

https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html

As we are by latency you may need this, as well.

http://www.alsa-project.org/main/index.php/Low_latency_howto

Cheers,
Joël