CoreXL Dynamic Balancing

Product: Check Point Appliances, CoreXL, ElasticXL, Maestro HyperScale Firewall, Scalable Chassis, Security Gateways, VSNext, VSX (Traditional)

Version: R80.40 (EOS), R81 (EOS), R81.10 (EOS), R81.20, R82, R82.10

OS: Gaia

Last Modified: 2026-06-14

Solution

Table of Contents

• Introduction
• Key Features
• System Requirements
• CLI Syntax
• Advanced Configuration Parameters
• Monitoring
• SmartConsole Extension
• Super Instance Feature
• Turbo Boost Feature
• "Green" Feature
• HyperFlow Resource Allocation
• FAQ
• Notes
• Known Limitations

Introduction

Security Gateway R80.40 and higher contains the CoreXL Dynamic Balancing (formerly, Dynamic Split) feature - a performance-enhancing daemon that balances the load between CoreXL SND instances and CoreXL Firewall instances. It dynamically changes the split between CoreXL SND instances and CoreXL Firewall instances and does not require a reboot or cause an outage.

Each Check Point Security Gateway's CPU belongs to one of two groups, each of which performs a different task:

• CoreXL Firewall Instance
• CoreXL SND (with the exception of a single CPU running FWD in large User-Space appliances).

The distribution of jobs across a Security Gateway's CPU cores is referred to as the Security Gateway's split. As the distribution of work across these groups depends on your security policy and traffic, we highly recommend that you configure your split to fit your specific needs.

CoreXL's Out-of-the-Box Dynamic Balancing performs a dynamic change of the split. It monitors the Security Gateway performance and makes changes as needed.

Default State:

• CoreXL Dynamic Balancing is enabled by default in the versions R81 and higher.
• CoreXL Dynamic Balancing is disabled by default in the R80.40 version.

Key Features

• Out-of-the-box optimization
• A flexible split to suit your profile

System Requirements

CLI Syntax

For the complete procedures, refer to the Performance Tuning Administration Guide for your version > Chapter " CoreXL" > Section " Performance Tuning" > Section " Dynamic Balancing of CoreXL Instances".

Important - In ClusterXL, you must configure all cluster members in the same way. In High Availability mode, start with the Standby members.

Syntax

Advanced Configuration Parameters

CoreXL Dynamic Balancing has various configuration parameters that you can change during the run-time.

CLI Syntax:

Availability:

• R81.20 and higher
• R81.10 Jumbo Hotfix, Take 79 or higher
• R81 Jumbo Hotfix, Take 77 or higher
• R80.40 Jumbo Hotfix, Take 180 or higher

Monitoring

• You can see the CoreXL Dynamic Balancing status in CPView ( sk101878) > SysInfo tab.

• You can monitor the CoreXL Dynamic Balancing performance in CPView > CPU tab.

• You can monitor the CoreXL Dynamic Balancing actions in these log files on the Security Gateway / Scalable Platform Security Group:

  • $FWDIR/log/dynamic_split.elg
  • $FWDIR/log/dsd.elg

SmartConsole Extension

You install the SmartConsole Extension " CoreXL Dynamic Balancing" to monitor and control CoreXL Dynamic Balancing.

In SmartConsole:

1. From the left navigation panel, click Manage & Settings.
2. Click Preferences.
3. In the SmartConsole Extensions section, click [+] ( Import).
4. Paste this URL and click OK:

https://dannyjung.de/ds.json

Super Instance Feature

The Super Instance feature is supported in these versions ( not supported in the VSX mode):

• R81.20 and higher
• R81.10 Jumbo Hotfix Take 79 or higher
• R81 Jumbo Hotfix Take 77 or higher
• R80.40 Jumbo Hotfix Take 180 or higher

Turbo Boost Feature

Only these software versions support Intel Turbo Boost:

• R82.10 and higher: Turbo Boost is enabled by default.
• R82 Jumbo Hotfix Take 25 or higher: Turbo Boost is supported.

"Green" Feature

The "Green" feature reduces power consumption on Check Point Appliances during low-load conditions by dynamically applying power-saving optimizations. See sk184700.

HyperFlow Resource Allocation

In R81.20 and higher, alongside the regular CoreXL split decisions, CoreXL Dynamic Balancing is responsible for activation of HyperFlow cores (refer to sk178070 - HyperFlow in R81.20 and higher).

FAQ

• Who should use Dynamic Balancing?

Dynamic Balancing is especially beneficial for:

• Customers who use non-default splits
• Customers with environment bottle-necks by Secure Network Distributors (SNDs)
• Customers with environments that may change usage over time - you can "auto tune" your Security Gateway with no outages, no reboots, no need for any skills!

• Why don't I get more Secure Network Distributors (SNDs)?

There are few possible reasons:

• Average utilization of CoreXL SND instances vs. CoreXL Firewall instances is relatively close (the default required difference is 10%).
• CoreXL Firewalls are utilized more than 50%. ( This is done to prevent a situation where more than one heavily utilized CoreXL Firewall instance works on a single CPU.
• All eligible SND CPU cores are already used as CoreXL SND instances.

• Why don't I get more Firewalls?

There are few possible reasons:

• Average utilization of CoreXL SND instances vs. CoreXL Firewall instances is relatively close (the default required difference is 10%).
• All loaded CoreXL Firewall instances are already active.

• How does it work with Cluster?

In Cluster High Availability mode, changes the Active cluster member makes are synchronized to the Standby cluster members. This does not apply to VRRP clusters.

• Can excessive split changes impact production environment?

CoreXL Dynamic Balancing has mechanisms within its logic aimed to prevent unwanted changes.

Notes

CoreXL Dynamic Balancing manages network card ports that have Multi-Queue enabled.

Known Limitations