---
title: "Comment by Edge Ops on \"Measuring web application firewall performance: real numbers from private cloud deployments\" | Hashnode"
description: "WAF performance numbers only help when the test traffic matches production shape. Prefer measuring p50/p95/p99 latency and allowed RPS with the same rule set an"
url: "https://hashnode.com/posts/measuring-web-application-firewall-performance-real-numbers-from-private-cloud-deployments/69ec756b611f78f9035950d5/comment/6af24614b9e17432e02e2ac3"
---

[Discussion](https://hashnode.com/posts/measuring-web-application-firewall-performance-real-numbers-from-private-cloud-deployments/69ec756b611f78f9035950d5)

Comment [Measuring web application firewall performance: real numbers from private cloud deployments](https://hashnode.com/posts/measuring-web-application-firewall-performance-real-numbers-from-private-cloud-deployments/69ec756b611f78f9035950d5)

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 9](https://hashnode.com/posts/measuring-web-application-firewall-performance-real-numbers-from-private-cloud-deployments/69ec756b611f78f9035950d5/comment/6af24614b9e17432e02e2ac3)

WAF performance numbers only help when the test traffic matches production shape. Prefer measuring p50/p95/p99 latency and allowed RPS with the same rule set and TLS offload path you will run live, keep a detection-only canary before flipping to block so false positives show up as labels not outages, and separate rule-eval cost from origin time so a slow backend does not look like a WAF regression.

Ops prove-out after a rule or engine change: replay a clean canary corpus and a known-bad payload set under the new profile, then compare blocked and allowed counts plus edge latency against the previous baseline for one deploy window. If p95 climbs while origin CPU stays flat, the new rule group is doing extra work on every request — tighten matches or move noisy rules to count. Under a synthetic flood, confirm rate or challenge actions trip before origin saturation; if origin request rate still tracks the attack, the WAF is still in detect mode where you think you are blocking.
