Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Wolfgang
Authority
Authority
Jump to solution

dynamic balancing, question for adding new SND core

Following Dynamic Balancing of CoreXL Instances an automatic assignment of SNDs is possible. But how it works, I don’t get it ☹

################################################################

  • Add a CoreXL SND instance.

This change stops a CoreXL Firewall instance and moves it to another CPU core.

This change is possible only under these conditions:

               a. Average difference in CPU utilization between CoreXL Firewall and SND instances is greater than 10%.

               b. CoreXL Firewall instances consume the CPU cores at less than 40%.

                c. There is an available CPU core.

################################################################

Please, can someone give more details and explain the conditons when a new SND will be added.

„Average difference in CPU utilization“, to get this point…… Average of all SND cores and all CoreXL cores ?

Paragraph b. „CoreXL Firewall instances consume the CPU cores at less than 40%“ Less 40% of what ? number of cores, CPU utilization of all CoreXL cores ?

 

0 Kudos
1 Solution

Accepted Solutions
Timothy_Hall
Legend Legend
Legend

sk164155 will answer all your questions, an adjustment will not be made unless there is LESS than 60% utilization (or 40% idle) on the type of cores being examined (SND or FW Instance), see variables in that SK such as SUPER_INST_ADD_FW_LOAD & DMD_WAKEUP_FW_LOAD which are set to 60. 

Generally unless there is at least 40% idle "headroom" on the type of CPUs being examined, a split adjustment or initiating Hyperflow will probably not happen.  The goal of Dynamic Split and Hyperflow is to let traffic and elephant flows move as fast as they want, but only if a headroom of 40% idle can be maintained to respect the "mice" connections and keep them from getting stomped by a couple of big mean elephants or even by the overall traffic load.

Gateway Performance Optimization R81.20 Course
now available at maxpowerfirewalls.com

View solution in original post

4 Replies
PhoneBoy
Admin
Admin

It's the aggregate average usage of CoreXL/worker instances versus the aggregate average usage of SND/SecureXL instances.
If the aggregate average of all CoreXL/worker instances is at least 40%, we do not take a CoreXL/Worker instance for SND as that will likely make things worse.

0 Kudos
Timothy_Hall
Legend Legend
Legend

sk164155 will answer all your questions, an adjustment will not be made unless there is LESS than 60% utilization (or 40% idle) on the type of cores being examined (SND or FW Instance), see variables in that SK such as SUPER_INST_ADD_FW_LOAD & DMD_WAKEUP_FW_LOAD which are set to 60. 

Generally unless there is at least 40% idle "headroom" on the type of CPUs being examined, a split adjustment or initiating Hyperflow will probably not happen.  The goal of Dynamic Split and Hyperflow is to let traffic and elephant flows move as fast as they want, but only if a headroom of 40% idle can be maintained to respect the "mice" connections and keep them from getting stomped by a couple of big mean elephants or even by the overall traffic load.

Gateway Performance Optimization R81.20 Course
now available at maxpowerfirewalls.com
Wolfgang
Authority
Authority

Thanks @Timothy_Hall you're right Dynamic Balancing for IPv4 CoreXL Instances answers all.

0 Kudos
Chris_Atkinson
Employee Employee
Employee

Tagging @AmitShmuel in case further clarification is needed on any areas.

CCSM R77/R80/ELITE

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events