Performance issues that Test/UAT couldn’t predict
PowerBuilder client/server applications typically connect directly from client to database. That architecture has no standard HTTP/API layer for load testing tools to intercept — which makes SLA-style performance testing extremely difficult. Citrix adds another layer of opacity.
🧱 No HTTP layer
In classic client/server, data calls are client→DB via binary drivers (ODBC/OLE DB). Tools like JMeter/LoadRunner need HTTP/API traffic to record/replay.
🖥️ Citrix masks transactions
Citrix sessions are effectively pixels/remote UI. Transaction-level API replay and measurement are not naturally available.
🔥 Release risk
Without measurable pre‑release load profiles, a “small change” can trigger major performance regressions in production.
Key insight: the bottleneck wasn’t only code — it was the inability to measure and reproduce workload behavior using standard load testing tools.