- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Following Dynamic Balancing of CoreXL Instances an automatic assignment of SNDs is possible. But how it works, I don’t get it ☹
################################################################
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 ?
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.
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.
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.
Thanks @Timothy_Hall you're right Dynamic Balancing for IPv4 CoreXL Instances answers all.
Tagging @AmitShmuel in case further clarification is needed on any areas.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 20 | |
| 19 | |
| 18 | |
| 8 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY