Full-Core PPPoE · every CPU core carries its share · more capacity · lower latency · lower cost/sub
Engine Brief · Full-Core Performance
Full-Core PPPoE — every CPU core carries its share, even for PPPoE
Here is a quiet, expensive secret of every PPPoE broadband network: the network card cannot spread PPPoE traffic across your CPU cores. It all funnels onto one core — which maxes out while every other core sits idle — so a twelve-core box hits the wall at a fraction of what you paid for, and your subscribers feel it as lag and stutter on a machine that is mostly asleep. BNGSOFT Full-Core PPPoE fixes it in software: it opens the PPPoE envelope, identifies each subscriber's traffic, and fans the load evenly across every core. Same hardware, far more of it working.
The network card spreads ordinary internet traffic across all your cores automatically. For PPPoE it simply can't see inside the envelope — so it dumps everything on core #1. BNGSOFT opens the envelope and shares the load. The cores you already paid for finally all show up for work.
All cores
not just one
PPPoE load fanned evenly across every CPU core
More per box
headroom unlocked
use the full machine — more subscribers, same tin
Lower latency
no saturated core
smoother, steadier under peak — better experience
Zero-downtime
default-off · fail-safe
a software switch — no reboot, no new hardware
1 · The hidden bottleneck: one core does all the PPPoE work
Modern network cards are built to share load. They look at each connection — who it's from, who it's to — and hand it to a different CPU core, so a busy box spreads its work evenly and uses all of its cores. It works beautifully… for ordinary internet traffic.
PPPoE is different. On a fibre or DSL network, each subscriber's traffic is wrapped in a PPPoE envelope — and the network card can't read the address inside the envelope. Unable to tell one subscriber's flow from another, it does the only thing it can: it drops every PPPoE packet onto the same single core.
The result: one CPU core runs flat-out at 100% and becomes the bottleneck for the whole box, while the other cores sit nearly idle. The machine tops out — dropping packets, adding lag — at a fraction of the throughput its hardware is capable of. You bought twelve lanes of motorway; PPPoE forces every car into lane one.
Why it matters to the business: it's a tax you pay twice — once in capacity (you buy extra boxes to work around a bottleneck that has nothing to do with real load) and once in experience (subscribers hit lag during peak hour on a box that's 80% idle).
2 · The idea — open the envelope, share the load
BNGSOFT does in software the one thing the network card can't: it looks inside the PPPoE envelope, reads which subscriber flow each packet belongs to, and steers it to a fair share of every core — instantly, in the fast path, before any heavy work happens. The load the card couldn't spread, BNGSOFT spreads.
ILLUSTRATIVE Left: the card can't read PPPoE, so one core takes everything and caps the box. Right: BNGSOFT reads each subscriber flow and fans it evenly, so the whole machine works.
Per-subscriber fair, not random: each subscriber's flow is kept together on its chosen core (so nothing gets reordered), while different subscribers are spread across the cores. The result is even load and clean, in-order delivery.
3 · What it delivers
CAPACITY
More subscribers per box.
The bottleneck was never your real traffic — it was one pinned core. Remove it and the whole machine's CPU is available.
Throughput scales with the core count you already own, not with a single core's ceiling.
Grow your subscriber base on the same hardware — or consolidate onto fewer boxes.
EXPERIENCE
Lower, steadier latency at peak.
No single saturated core means no queue building behind it — less lag, less jitter exactly when the network is busiest.
Smoother video calls, gaming and streaming for subscribers during the evening peak.
Fewer “it's slow at 8 pm” support tickets rooted in a hidden CPU wall.
ECONOMICS
Lower cost per subscriber.
Using the full box means fewer boxes for the same subscriber count — less capex, rack space, power and support.
Defers the next hardware refresh: headroom you already paid for is unlocked in software.
A software switch — no forklift, no new line cards.
4 · Proven on a live network
On a production BNGSOFT box carrying thousands of PPPoE subscribers, the PPPoE bottleneck was measured directly: the single “catch-all” path was carrying roughly 26× more traffic than a fair share — one core pinned while the rest coasted. With Full-Core PPPoE switched on, that load fanned out evenly across all twelve cores.
On the live box
Before — card only
With Full-Core PPPoE
PPPoE load distribution
~26× on one core, rest idle
~1× — even across every core
Usable capacity
Capped by a single core
Full box — all cores working
Latency behaviour at peak
Builds behind the hot core
Smoother, no single wall
Packets dropped switching it on
—
Zero · seamless, live
Switched on live, with zero packet loss. No maintenance window, no reboot, no subscriber disruption — the load simply rebalanced from “one core doing everything” to “every core doing its share.”
5 · Safe by design
Default-off, operator-controlled
Ships inert. You turn it on with a single setting when you're ready — and it stays on across restarts.
Fail-safe
If a core is ever momentarily unavailable, the packet simply follows the normal path — it is never dropped. There is no failure mode that loses traffic.
Order-preserving
Each subscriber's flow stays pinned to one core, so packets never arrive out of order — the network card's own guarantee, kept.
No new hardware, no reboot
Pure software in the BNGSOFT fast path. Enable and disable live; nothing to install, nothing to cable.
“We were sizing the next box purchase around a CPU ceiling that turned out to be one pinned core, not real load. Turning on Full-Core PPPoE gave the whole machine back — same tin, far more headroom.”
— The problem Full-Core PPPoE was built to end
6 · Where it fits
GROWING
Running out of headroom
One core near 100% at peak; the rest idle.
A hardware purchase looming to “add capacity.”
Outcome: unlock the box you own before buying another.
PEAK-HOUR
Evening lag complaints
Subscribers report stutter at 8–11 pm.
Box CPU “looks fine” on average — because it's one core.
Outcome: remove the hidden wall; smoother peak.
CONSOLIDATING
Fewer boxes, same subscribers
A fleet sized around a per-core PPPoE cap.
High rack, power and support overhead.
Outcome: pack more subscribers per box; shrink the fleet.
Full-Core PPPoE — stop paying for cores you can't use
PPPoE forces every subscriber onto one CPU core and caps a multi-core box at a fraction of its worth. BNGSOFT opens the PPPoE envelope, reads each subscriber flow, and fans the load evenly across every core — so you get more subscribers per box, steadier latency at peak, and a lower cost per subscriber, from the hardware you already own.
Zero-downtime. Default-off. Fail-safe. A software switch — no reboot, no new hardware.
Figures cited (“~26× on one core”, “zero packet loss”) are from a live BNGSOFT production deployment carrying several thousand PPPoE subscribers; exact numbers vary with hardware, core count, subscriber mix and traffic. Diagrams are illustrative. Full-Core PPPoE distributes the software-processing load of PPPoE subscriber traffic across CPU cores; per-subscriber flow ordering is preserved. Default-off and fail-safe: with the feature off, or a target core unavailable, traffic follows the standard path unchanged. Availability and behaviour depend on network-card and platform support.