> Source: [sk122013](https://support.checkpoint.com/results/sk/sk122013)

# sk122013 - Handling heavy connections in CoreXL

| Property | Value |
|----------|-------|
| Solution ID | sk122013 |
| Date Created | 2017-12-21 |
| Last Modified | 2021-08-19 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- A single connection/FW instance core is highly utilizing a single CoreXL instance while other cores are not.

## Cause

* Our Software architecture dictates that each connection (identified by source, destination, source port, destination port and IP protocol) will be assigned to a single FW core, or CoreXL instance.

<!-- -->

* If a particular connection contains a large chunk of data transfer (high data packets rate), the single CoreXL instance will get highly utilized resulting in drops, retransmissions and/or latency.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content