<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Priority Queueing Trigger Time? in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Priority-Queueing-Trigger-Time/m-p/176439#M32307</link>
    <description>&lt;P&gt;The Priority Queueing feature deprioritizes the packets of an identified elephant/heavy flow when the CPU utilization of a individual Firewall Worker Instance reaches 100%.&amp;nbsp; My question is for how long must the CPU utilization of that Firewall Worker Instance be at 100% before Priority Queueing kicks in?&amp;nbsp; This doesn't appear to be documented; all the official documentation and SKs just say that Priority Queueing becomes active when the core reaches 100%.&lt;/P&gt;
&lt;P&gt;Poking around in the Firewall Worker Instance kernel variables, there is an undocumented variable that may be related:&lt;/P&gt;
&lt;P&gt;fwmultik_prio_grace_thld = 300&lt;/P&gt;
&lt;P&gt;I'm assuming the 300 indicates 300 milliseconds, so is the answer 0.3 seconds?&amp;nbsp; That seems like a reasonable value.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Mar 2023 16:28:09 GMT</pubDate>
    <dc:creator>Timothy_Hall</dc:creator>
    <dc:date>2023-03-28T16:28:09Z</dc:date>
    <item>
      <title>Priority Queueing Trigger Time?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Priority-Queueing-Trigger-Time/m-p/176439#M32307</link>
      <description>&lt;P&gt;The Priority Queueing feature deprioritizes the packets of an identified elephant/heavy flow when the CPU utilization of a individual Firewall Worker Instance reaches 100%.&amp;nbsp; My question is for how long must the CPU utilization of that Firewall Worker Instance be at 100% before Priority Queueing kicks in?&amp;nbsp; This doesn't appear to be documented; all the official documentation and SKs just say that Priority Queueing becomes active when the core reaches 100%.&lt;/P&gt;
&lt;P&gt;Poking around in the Firewall Worker Instance kernel variables, there is an undocumented variable that may be related:&lt;/P&gt;
&lt;P&gt;fwmultik_prio_grace_thld = 300&lt;/P&gt;
&lt;P&gt;I'm assuming the 300 indicates 300 milliseconds, so is the answer 0.3 seconds?&amp;nbsp; That seems like a reasonable value.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 16:28:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Priority-Queueing-Trigger-Time/m-p/176439#M32307</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2023-03-28T16:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: Priority Queueing Trigger Time?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Priority-Queueing-Trigger-Time/m-p/176493#M32312</link>
      <description>&lt;P&gt;Wow, I can’t even find that kernel variable in internal SKs/SRs.&lt;BR /&gt;Maybe&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/8659"&gt;@Chen_Muchtar&lt;/a&gt;&amp;nbsp;knows.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 22:22:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Priority-Queueing-Trigger-Time/m-p/176493#M32312</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-03-28T22:22:10Z</dc:date>
    </item>
  </channel>
</rss>

