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

 
 
Latest News
OSC client to server communication succeeded posted by jkraehemann, Sat 15 Dec 2018 09:31:38 PM UTC - 0 replies
Advanced Gtk+ Sequencer v2.1.2 released posted by jkraehemann, Fri 30 Nov 2018 06:55:47 PM UTC - 0 replies
Implementing AgsOscServer and related controllers posted by jkraehemann, Thu 22 Nov 2018 07:35:34 AM UTC - 0 replies
Advanced Gtk+ Sequencer v2.1.x - implementing server parts posted by jkraehemann, Sun 04 Nov 2018 11:53:45 PM UTC - 0 replies
Extending the test-suite of v2.0.x posted by jkraehemann, Wed 10 Oct 2018 02:38:35 AM UTC - 0 replies
[Submit News]
[70 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.3