documentation:examples:ipsec_performance_of_a_netgate_rcc-ve_4860
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:examples:ipsec_performance_of_a_netgate_rcc-ve_4860 [2020/09/22 12:04] – [Using IPSec bench "Equilibrium throughput" method] olivier | documentation:examples:ipsec_performance_of_a_netgate_rcc-ve_4860 [2020/09/22 12:08] (current) – [Using IPSec bench "Equilibrium throughput" method] olivier | ||
|---|---|---|---|
| Line 155: | Line 155: | ||
| Once done, we start using a fast method for measuring the "IPsec equilibrium throughput" | Once done, we start using a fast method for measuring the "IPsec equilibrium throughput" | ||
| - | |||
| - | Notice that the reference device (IBM x3550-M3) used in front of the Netgate has a [[IPSec performance lab of an IBM System x3550 M3 with Intel 82580|equilibrium throughput of 843Mb/s]]. Then if the value measured during this bench is close to 843Mb/s we had to found a more powerful reference device. | ||
| From the packet generator/ | From the packet generator/ | ||
| Line 205: | Line 203: | ||
| Using AES-GCM-128 and aesni kernel module loaded on the NetGate RCC-VE 4860, we can estimate an IPSec Equilibrium throughput of about 672Mb/s. | Using AES-GCM-128 and aesni kernel module loaded on the NetGate RCC-VE 4860, we can estimate an IPSec Equilibrium throughput of about 672Mb/s. | ||
| - | {{bench-ipsec-netgate-13head.png}} | + | {{bench.netgate.ipsec.13head.png}} |
documentation/examples/ipsec_performance_of_a_netgate_rcc-ve_4860.1600769042.txt.gz · Last modified: 2020/09/22 12:04 by olivier