No subject

as routing daemon using single socket 4 core Intel Xeon X3470 (2.93 Ghz=
),
with 4GB RAM and 4 multiqueue NIC (like Intel 82576, 82580, ...) routes=
 1,5 -
1,8 Gbit/sec at PPS ~300 000 with ~ 98% of CPU time spent at the lowest=

frequency (1.2 Ghz). Software part is custom Linux distribution based o=
n
Debian GNU/Linux 7.x (wheezy), and custom Linux kernel based on 3.2 sta=
ble=20
branch, build for x86_64 architecture.

So Intel Xeon X3470 is much likely very powerful for such setups (pure
forwarding with no traffic policy).

On other deployments I have similar results:

CPU: Intel Xeon X3470, 2.93
RAM: 2GB-6GB

Task:
Dual stack IPv4/IPv6, shaping with HTB (U32 hash classifier),
802.1ad (QinQ) to customer end (this turns off hardware offloading task=
s
on NICs), uRPF (Reverse Path filtering from customer side to prevent IP=

spooofing) for both IPv4/IPv6, few iptables rules (connection tracking =
is
turned off) and aggressive ipset usage (billing hooks, DDoS, etc).

Traffic (In:Out): 2Gbit/sec:1.5Gbit/sec, PPS <450 000.

Peak load: <80% on all cores.

Also having threads (Hyper-Threading) has no good effect on traffic for=
warding
workloads, as CPU cache is shared between physical cores, causing more =
cache
misses and thus lower performance.

Amount of RAM seems not wery important, hardware with starting from 2GB=
 RAM=20
sizes is enough to store routing cache information.


>=20
> Thanks to the dev team, and kind regards.
>=20
> Tigran Zakoyan.

--=20
SP5474-RIPE
Sergey Popovich