newsAdvanced Gtk+ Sequencer - News: It's about systemd and performance

 
 
Latest News
GSequencer v3.6.x release goals posted by jkraehemann, Fri 31 Jul 2020 10:17:04 AM UTC - 0 replies
GSequencer v3.4.x release goals posted by jkraehemann, Thu 11 Jun 2020 06:58:14 PM UTC - 0 replies
GSequencer v3.3.x replaced all recalls by ags-fx engine posted by jkraehemann, Wed 20 May 2020 07:25:15 AM UTC - 0 replies
Refactor GSequencer's recalls - the ags-fx engine posted by jkraehemann, Sun 03 May 2020 12:08:19 AM UTC - 0 replies
GSequencer v3.3.x release goals posted by jkraehemann, Fri 17 Apr 2020 12:36:11 PM UTC - 0 replies
[Submit News]
[97 news in archive]

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

No messages in It's about systemd and performance

 

Back to the top


Powered by Savane 3.5