<?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 Re: CPU Affinity in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/CPU-Affinity/m-p/86357#M6672</link>
    <description>&lt;P&gt;I'm not sure why you would want to do that on a 2-core firewall, I assume since it is standalone you want all firewall workers and SND's sharing core 0 while SMS management functions use core 1?&amp;nbsp; Your performance will almost certainly be terrible since there will be so many CoreXL components fighting each other for a single core, what you might want to do instead is disable CoreXL completely from &lt;STRONG&gt;cpconfig&lt;/STRONG&gt; which should give you one SND on Core 0 and one Firewall Worker on Core 1.&amp;nbsp; Management processes will take a backseat to kernel operations occurring in the single SND and single Firewall Worker.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you want to do it anyway, you'll need to configure the fwaffinity.conf file, see&amp;nbsp;&lt;SPAN&gt;&lt;A class="cp_link sc_ellipsis" href="https://sc1.checkpoint.com/documents/R80.30/WebAdminGuides/EN/CP_R80.30_PerformanceTuning_AdminGuide/html_frameset.htm" target="_blank" rel="noopener"&gt;R80.30 Performance Tuning Administration Guide&lt;/A&gt;.&amp;nbsp; In general though setting up manual affinity is not a desirable path to start down if it can be avoided.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 26 May 2020 15:05:02 GMT</pubDate>
    <dc:creator>Timothy_Hall</dc:creator>
    <dc:date>2020-05-26T15:05:02Z</dc:date>
    <item>
      <title>CPU Affinity</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/CPU-Affinity/m-p/86348#M6671</link>
      <description>&lt;P&gt;Hello!&lt;BR /&gt;How can I configure to set manually the process "Kernel fw_0" must be processed by CPU-0?&lt;BR /&gt;See the attachment to see what I mean.&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2020 14:28:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/CPU-Affinity/m-p/86348#M6671</guid>
      <dc:creator>Fernandosilva</dc:creator>
      <dc:date>2020-05-26T14:28:59Z</dc:date>
    </item>
    <item>
      <title>Re: CPU Affinity</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/CPU-Affinity/m-p/86357#M6672</link>
      <description>&lt;P&gt;I'm not sure why you would want to do that on a 2-core firewall, I assume since it is standalone you want all firewall workers and SND's sharing core 0 while SMS management functions use core 1?&amp;nbsp; Your performance will almost certainly be terrible since there will be so many CoreXL components fighting each other for a single core, what you might want to do instead is disable CoreXL completely from &lt;STRONG&gt;cpconfig&lt;/STRONG&gt; which should give you one SND on Core 0 and one Firewall Worker on Core 1.&amp;nbsp; Management processes will take a backseat to kernel operations occurring in the single SND and single Firewall Worker.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you want to do it anyway, you'll need to configure the fwaffinity.conf file, see&amp;nbsp;&lt;SPAN&gt;&lt;A class="cp_link sc_ellipsis" href="https://sc1.checkpoint.com/documents/R80.30/WebAdminGuides/EN/CP_R80.30_PerformanceTuning_AdminGuide/html_frameset.htm" target="_blank" rel="noopener"&gt;R80.30 Performance Tuning Administration Guide&lt;/A&gt;.&amp;nbsp; In general though setting up manual affinity is not a desirable path to start down if it can be avoided.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2020 15:05:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/CPU-Affinity/m-p/86357#M6672</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2020-05-26T15:05:02Z</dc:date>
    </item>
  </channel>
</rss>

