<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Linux Runtime Tuning</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/8ce3de5aaa/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Runtime/thread/8ce3de5aaa/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Runtime/thread/8ce3de5aaa/</id><updated>2020-07-28T16:52:30.249000Z</updated><subtitle>Recent posts to Linux Runtime Tuning</subtitle><entry><title>Linux Runtime Tuning</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/8ce3de5aaa/?limit=25#a17d" rel="alternate"/><published>2020-07-28T16:52:30.249000Z</published><updated>2020-07-28T16:52:30.249000Z</updated><author><name>adverb</name><uri>https://forge.codesys.com/u/adverb/</uri></author><id>https://forge.codesys.com52e4b977c203a1e10fa7dfa76c2197f72abf02e7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi all.  cpupower utility was helpful in setting governor to 'performance' mode in Debian, which appears to help stabilize/lower cyclictest numbers, even while under stress-ng loads.  Any tips for debugging outliers?  I mean to say, debugging a missed latency target, by tracing kernel to find the cause?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Linux Runtime Tuning</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/8ce3de5aaa/?limit=25#ece6/2e3b" rel="alternate"/><published>2020-07-13T11:45:46.977000Z</published><updated>2020-07-13T11:45:46.977000Z</updated><author><name>Ingo</name><uri>https://forge.codesys.com/u/ingo/</uri></author><id>https://forge.codesys.com7f5ba65ca68e76981911d21d98536f758148ccfb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="nv"&gt;It&lt;/span&gt; &lt;span class="nv"&gt;would&lt;/span&gt; &lt;span class="nv"&gt;be&lt;/span&gt; &lt;span class="nv"&gt;ideal&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nv"&gt;Codesys&lt;/span&gt; &lt;span class="nv"&gt;could&lt;/span&gt; &lt;span class="nv"&gt;compile&lt;/span&gt; &lt;span class="nv"&gt;a&lt;/span&gt; &lt;span class="nv"&gt;whitepaper&lt;/span&gt; &lt;span class="nv"&gt;with&lt;/span&gt; &lt;span class="nv"&gt;their&lt;/span&gt; &lt;span class="nv"&gt;most&lt;/span&gt; &lt;span class="nv"&gt;common&lt;/span&gt; &lt;span class="nv"&gt;practices&lt;/span&gt; &lt;span class="nv"&gt;and&lt;/span&gt; &lt;span class="nv"&gt;suggestions&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;help&lt;/span&gt; &lt;span class="nv"&gt;Linux&lt;/span&gt; &lt;span class="nv"&gt;runtime&lt;/span&gt; &lt;span class="nv"&gt;customers&lt;/span&gt; &lt;span class="nv"&gt;get&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;best&lt;/span&gt; &lt;span class="nv"&gt;performance&lt;/span&gt; &lt;span class="nv"&gt;possible&lt;/span&gt;. &lt;span class="nv"&gt;But&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="nv"&gt;now&lt;/span&gt;, &lt;span class="nv"&gt;perhaps&lt;/span&gt; &lt;span class="nv"&gt;we&lt;/span&gt; &lt;span class="nv"&gt;can&lt;/span&gt; &lt;span class="nv"&gt;work&lt;/span&gt; &lt;span class="nv"&gt;together&lt;/span&gt; &lt;span class="nv"&gt;in&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;forum&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;share&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="nv"&gt;learn&lt;/span&gt;.
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;There is no release planned, yet, but it is on our list!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Linux Runtime Tuning</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/8ce3de5aaa/?limit=25#ece6" rel="alternate"/><published>2020-07-10T15:53:53.426000Z</published><updated>2020-07-10T15:53:53.426000Z</updated><author><name>adverb</name><uri>https://forge.codesys.com/u/adverb/</uri></author><id>https://forge.codesys.com7fa83b14dcd3f86a0c80e122cc76641c2313fd8d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello Codesys Community,&lt;/p&gt;
&lt;p&gt;When searching for term 'rt_preempt' there are past questions on the topic of reducing jitter on the Codesys Linux runtime, running on a Debian-based OS.  I found these suggestions:&lt;br/&gt;
&lt;em&gt; Use of the RT_PREEMPT kernel patch&lt;br/&gt;
&lt;/em&gt; Ensure stable CPU clock&lt;br/&gt;
* Use of CyclicTest tool for diagnostics&lt;/p&gt;
&lt;p&gt;To further improve performance (reduce jitter), are there additional suggestions from Codesys or the others in the community?  For example:&lt;br/&gt;
&lt;em&gt; Debugging kernel latency&lt;br/&gt;
&lt;/em&gt; Building a smaller/"lighter" kernel&lt;br/&gt;
&lt;em&gt; CPU isolation/pinning&lt;br/&gt;
&lt;/em&gt; others?&lt;/p&gt;
&lt;p&gt;It would be ideal if Codesys could compile a whitepaper with their most common practices and suggestions to help Linux runtime customers get the best performance possible.  But for now, perhaps we can work together in the forum to share/learn.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>