Forum Discussion
BIG-IP SSL orchestrator Throughput vs platform Throughput
- Aug 22, 2022
The platform data sheet is giving you raw throughput for the device. And for SSL (TLS handshake and encryption) these numbers reflect a single decrypt operation.
SSL Orchestrator throughput differs then in the following ways:
- SSL is almost always decrypt AND re-encrypt, so would theoretically be half of the platform SSL numbers.
- SSL forward proxy requires the BIG-IP to forge the server certificate to the client, which is a heavier function. That's why forward proxy and reverse numbers in the SSL Orchestrator data sheet are different.
- SSL Orchestrator uses CPU (compute) to drive traffic through the service chain, and is thus affected by the number of security devices in the chain. This is why the SSL Orchestrator data sheet provides different throughput numbers for 1, 2, and 3 devices.
- Aug 25, 2022
It is definitely worthwhile to start with SSLO 9.x (9.3 on BIG-IP 16.1.3 is the latest 9.x release as of Aug 2022).
The platform data sheet is giving you raw throughput for the device. And for SSL (TLS handshake and encryption) these numbers reflect a single decrypt operation.
SSL Orchestrator throughput differs then in the following ways:
- SSL is almost always decrypt AND re-encrypt, so would theoretically be half of the platform SSL numbers.
- SSL forward proxy requires the BIG-IP to forge the server certificate to the client, which is a heavier function. That's why forward proxy and reverse numbers in the SSL Orchestrator data sheet are different.
- SSL Orchestrator uses CPU (compute) to drive traffic through the service chain, and is thus affected by the number of security devices in the chain. This is why the SSL Orchestrator data sheet provides different throughput numbers for 1, 2, and 3 devices.
Kevin_Stewart Thanks.
Reading article Update or upgrade the F5 SSL Orchestrator | BIG-IP update and upgrade guide, sounds like SSL Orchestrator contains significant stability improvements in 16.1.x - 9.x. Since, we haven't provisioned SSL Orchestrator in v15.x devices, would it be wise to upgrade device to 16.1.x and provision/configure SSLO. I think this will help in us doing the workaround mentioned in the article.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com