<?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: ClusterXL Load Sharing vs Maestro Thrughtput in Hyperscale Firewall (Maestro)</title>
    <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/ClusterXL-Load-Sharing-vs-Maestro-Thrughtput/m-p/188032#M2136</link>
    <description>&lt;P&gt;The approaches are not equal, t&lt;SPAN&gt;raffic distribution &amp;amp; sync are performed differently in favor of Maestro achieving the much higher throughput.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Maestro has much lower overheads as additional members are added.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Note ElasticXL will be an alternate approach moving forward.&lt;/P&gt;</description>
    <pubDate>Sun, 30 Jul 2023 10:57:40 GMT</pubDate>
    <dc:creator>Chris_Atkinson</dc:creator>
    <dc:date>2023-07-30T10:57:40Z</dc:date>
    <item>
      <title>ClusterXL Load Sharing vs Maestro Thrughtput</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/ClusterXL-Load-Sharing-vs-Maestro-Thrughtput/m-p/188031#M2135</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It is highlighted that Maestro solution keep all the gateways in active - active state and hence throughput is increased (Number of GWs multiply by throughput of each GW).&lt;/P&gt;&lt;P&gt;As per my understanding, in&amp;nbsp;ClusterXL Load Sharing mode also, all GWs are in active state and processing the traffic in parallel so here also throughput should be increased as in Maestro.&lt;/P&gt;&lt;P&gt;What if&amp;nbsp;ClusterXL Load Sharing mode (unicast) and Maestro solution both have 2 GWs only? Throughput will be same in both cases or major difference. ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jaspal Singh&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jul 2023 10:38:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/ClusterXL-Load-Sharing-vs-Maestro-Thrughtput/m-p/188031#M2135</guid>
      <dc:creator>JSingh_N</dc:creator>
      <dc:date>2023-07-30T10:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: ClusterXL Load Sharing vs Maestro Thrughtput</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/ClusterXL-Load-Sharing-vs-Maestro-Thrughtput/m-p/188032#M2136</link>
      <description>&lt;P&gt;The approaches are not equal, t&lt;SPAN&gt;raffic distribution &amp;amp; sync are performed differently in favor of Maestro achieving the much higher throughput.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Maestro has much lower overheads as additional members are added.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Note ElasticXL will be an alternate approach moving forward.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jul 2023 10:57:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/ClusterXL-Load-Sharing-vs-Maestro-Thrughtput/m-p/188032#M2136</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-07-30T10:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: ClusterXL Load Sharing vs Maestro Thrughtput</title>
      <link>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/ClusterXL-Load-Sharing-vs-Maestro-Thrughtput/m-p/188047#M2137</link>
      <description>&lt;P&gt;What&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/3630"&gt;@Chris_Atkinson&lt;/a&gt;&amp;nbsp;said is 100% correct.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jul 2023 17:06:30 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/ClusterXL-Load-Sharing-vs-Maestro-Thrughtput/m-p/188047#M2137</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-07-30T17:06:30Z</dc:date>
    </item>
  </channel>
</rss>

