H700

H700 is the 1U entry-level TR7 hardware platform running on a 10-core Intel Xeon W processor. The values on this page are given with the workloads and metric definitions defined on the Test Methodology page; the condition of each value is stated in the related section.

The H700 platform is built on a 10-core Intel Xeon W processor. The TR7 software takes advantage of the hardware acceleration capabilities offered by the Intel processor and chipset in the cryptographic operations within TLS and in data compression. These workloads are processed efficiently by using the processor instructions, the acceleration resources supported by the platform and optimized software components together. The performance achieved depends on the algorithms used, the traffic characteristics and the configuration of the active services.

80 Gbps

Throughput

The highest value in the series, H780

1.8 M

HTTP requests/s

Over open connections, L7 service only

40,000

TLS TPS (ECDSA-P256)

Full handshake, ECDSA P-256

40 Gbps

TLS throughput

Bulk encryption on an established TLS connection

30 Gbps

Compression throughput

Pre-compression (input) bytes

9 M

L4 HTTP RPS

H760 and H780; L4 Concurrent Connections up to 120 M

Summary

Platform performance	H705	H710	H715	H720	H730	H740	H760	H780
Throughput	5 Gbps	10 Gbps	15 Gbps	20 Gbps	30 Gbps	40 Gbps	60 Gbps	80 Gbps
HTTP requests/s	1.2 M	1.2 M	1.4 M	1.6 M	1.8 M	1.8 M	1.8 M	1.8 M
TLS TPS (ECDSA-P256)	12,000	24,000	24,000	40,000	40,000	40,000	40,000	40,000
TLS throughput	5 Gbps	10 Gbps	10 Gbps	20 Gbps	30 Gbps	40 Gbps	40 Gbps	40 Gbps
Compression throughput	5 Gbps	10 Gbps	10 Gbps	16 Gbps	20 Gbps	30 Gbps	30 Gbps	30 Gbps
L4 HTTP RPS	1.2 M	3 M	3 M	5 M	8 M	8.5 M	9 M	9 M
L4 Concurrent Connections	20 M	57 M	57 M	80 M	120 M	120 M	120 M	120 M

Metric definitions: Metric Definitions. Value classes (measured and capacity): Value Classes.

Platform

Property	Value
Processor	Intel Xeon W, 10 cores
Onboard network	8 × GbE RJ-45 (copper), 2 × SFP; 2 pairs of LAN bypass
Expansion	2 network module slots (highest option 2 × 100 GbE QSFP28 / slot)
Storage	500 GB M.2 SSD
Power	1+1 redundant, 400 W
Form factor	1U · 44 × 430 × 561 mm

L7 HTTP

Metric	Condition
HTTP requests/s	Kept-open HTTP/1.1 connections; TR7 generates the response itself, no Backend Service

Since the requests arrive over open connections, the TCP handshake cost is not included in this value. The values belong to a device serving only L7; if L4 vServices are also defined on the same device, HTTP requests/s reads about 15% lower.

SSL/TLS

Metric	Condition
TLS TPS (ECDSA-P256)	Full handshake, session ticket off, TLS 1.2, cipher suite ECDHE-ECDSA-AES128-GCM-SHA256

The cryptographic operations within TLS take advantage of the hardware acceleration capabilities of the processor. In each full handshake, the device makes one ECDSA P-256 signature and performs the key exchange from scratch; the value scales with the number of processor cores.

Throughput

Metric	Path
Throughput	Full proxy, 64 KB object
TLS throughput	TR7's own response, 64 KB, TLS 1.3 AES-GCM

Model	Throughput	Delivered to the client	TLS throughput
H705	5 Gbps	2.5 Gbps	5 Gbps
H710	10 Gbps	5 Gbps	10 Gbps
H715	15 Gbps	7.5 Gbps	10 Gbps
H720	20 Gbps	10 Gbps	20 Gbps
H730	30 Gbps	15 Gbps	30 Gbps
H740	40 Gbps	20 Gbps	40 Gbps
H760	60 Gbps	30 Gbps	40 Gbps
H780	80 Gbps	40 Gbps	40 Gbps

Throughput is the sum of the two directions of the client and Backend Service legs; what is delivered to the client is half of this. The values are the traffic the processor can carry and are for 1500-byte frames; the achieved throughput is also limited by the line rate of the installed network modules. With the onboard copper and SFP ports, the line rate stays below the processor capacity; reaching the processor capacity requires 25, 40 or 100 GbE modules. TLS throughput is the bytes sent by the network card and includes the TLS, TCP/IP and frame headers.

Software Compression

Metric	Condition
Compression throughput	gzip, pre-compression (input) bytes

The device compresses the response in gzip format, at the fastest level. The value depends on the repetition ratio of the content: highly repetitive content such as table and report output compresses noticeably faster than an ordinary HTML page.

Content class	Ratio	Compressibility
Heavily repetitive: table and report output	35.10:1	97%
Moderately repetitive: JSON and log	9.62:1	90%
HTML: repeating template	5.47:1	82%
Real report page	3.60:1	72%

L4

Metric	Condition
L4 HTTP RPS	HTTP requests forwarded over established persistent connections; 1 million persistent connections, 128-byte requests, 8 Backend Services
L4 Concurrent Connections	Connections opened and kept idle; the value is the number of entries in the device's connection table

In an L4 vService, the device does not terminate the connection and does not read HTTP content; it forwards the packets of the established connection to the Backend Service. In L4 HTTP RPS, persistent connections are opened at the start of the run and reused throughout the run; the value is the requests sent per second.

In L4 Concurrent Connections, connections are opened and kept open with a 60-second idle period; the value is not the generator's count but the number of entries in the device's own connection table. The measurement setup is limited to 100.7 M connections by the address space of the load generator; values above this limit are in the Capacity class.