Silk Performer · /// Alternative
Silk Performer is heritage. LoadGen is the modern stack.
Silk Performer (now OpenText) has decades of enterprise QA heritage — but the cockpit is legacy and the scripting model dates back to the Borland era. LoadGen ships a wizard-driven, browser-native cockpit with Citrix HDX + AVD ARM-native depth, monitoring, DEM, and a visual API editor. Transparent pricing.
Wizard-driven, not script-basedCitrix HDX + AVD ARM nativeModern, browser-native cockpit
Side-by-side capability matrix — autoplay highlights every row.
The Fair Version
Silk Performer earned its install base.
No straw-man comparisons. Silk Performer has decades of enterprise QA heritage — these are the strengths a fair-minded buyer should know.
Long enterprise QA history
Silk Performer has been an enterprise load-testing fixture since the Borland era. Some teams have decades of scripts and CI patterns built around it.
OpenText suite integration
For organisations standardised on OpenText, Silk Performer integrates with the broader test-automation and ALM tooling.
Vendor-backed enterprise support
OpenText offers formal enterprise-support agreements — important for regulated-industry procurement that favours incumbent vendors.
Why teams move to LoadGen
Three places Silk Performer doesn’t reach.
Silk Performer was designed in an earlier era of enterprise QA. Teams modernising hit the same three friction points: legacy UI, no monitoring mode, no EUC-native depth for Citrix HDX / AVD ARM.
Modern, wizard-driven authoring
A 7-step wizard captures Citrix and AVD scenarios in minutes — no Silk Performer script to maintain, no legacy capture proxy. Native protocol depth out of the box.
Same engine, monitoring mode
The scenario that runs as a Silk Performer load test cannot fire as a continuous synthetic check. In LoadGen, the same .lgs scenario runs as both load test and synthetic user every minute.
SessionSight DEM + API testing in one
Silk Performer ships no DEM and a legacy script-based API model. LoadGen adds heatmaps + replay + journeys, plus a visual flow editor with 28 node types — same platform.
Modern cockpit
Browser-native — not a thick controller client.
Silk Performer ships a thick-client controller and a separate result-viewer. LoadGen runs entirely in the browser — KPIs, sessions table, time-range scrub, multi-test overlay all live.
- Per-step latency, p95 by protocol (HDX, ICA, AVD), error hotspots — visible during the run.
- Up to 5 runs overlaid on one chart.
- Same cockpit becomes the live monitoring view after cutover.
- No thick-client install, no remote-desktop hop into the controller.
Live cockpit — load and monitoring modes share one UI.
No-code API flows
A visual flow editor — not a Silk script.
28 node types, OpenAPI import, drag-drop authoring. End-to-end API validation lives inside the same platform as your load tests — no separate Silk script project.
- 28 node types: HTTP, REST, SQL, branching, loops, assertions, custom code, OpenAPI import.
- Drag-drop authoring — replayable as load AND as continuous synthetic checks.
- Captured once, replayed in both modes — no re-authoring across modes.
- Same Analytics + AI; alerts route to Email / Webhook / SMS / WhatsApp.
Visual flow editor — 28 node types, OpenAPI import.
What changes when you move
Three buying-decision metrics.
Before
Script + controller
After
Wizard + flow editor
Before
Load only
After
Testing + Monitoring + DEM + API
Before
Thick-client
After
Browser-native, real-time
Before
Suite licensing
After
Published
How teams move
Three patterns for replacing Silk Performer.
Modernise Citrix / AVD scenarios first
Keep Silk Performer on niche protocols still in use; move Citrix HDX and AVD ARM scenarios to LoadGen, where the wizards capture them natively.
See use caseConsolidate at OpenText renewal
At the next OpenText renewal cycle, evaluate replacing Silk Performer + separate monitoring + separate DEM with LoadGen.
See use caseBlock releases on regression
Wire LoadGen into the deploy pipeline. Block deploys on HDX p95 drift or API-flow error rate — instead of running an off-hours Silk Performer cycle.
See use caseSee LoadGen alongside Silk Performer on your stack.
We’ll author a Citrix or AVD scenario in the wizard on a call, fire it from a managed agent, and walk you through the live cockpit — no thick client, no Silk script project.
Questions
Frequently asked.
Does LoadGen replace Silk Performer, or run alongside it?
Most teams modernise one workload at a time. Citrix and AVD scenarios typically move to LoadGen first — wizard authoring is faster than Silk capture. Niche protocols in the Silk library can remain on Silk Performer until the next renewal cycle.
Can LoadGen import Silk Performer scripts?
No — the LoadGen authoring model is wizard + visual flow editor, not Silk script ingestion. For overlapping workloads (HTTP, REST, OpenAPI), re-authoring in the flow editor is typically faster than the original Silk capture.
How does LoadGen compare on enterprise-scale load?
The published Load Testing tier scales 50–25,000 vUsers; terms run from 1 week to 5 years. Full and VDI agents land per-session on real Citrix / AVD session hosts; Core agents handle HTTP workloads.
What does it cost compared to Silk Performer?
Silk Performer is licensed as part of the OpenText suite — pricing depends on bundle. LoadGen publishes €1,099 per week for Load Testing at the 50-vUser tier and €899 per Agent per month for End-to-End Monitoring.
Does LoadGen integrate with OpenText ALM?
LoadGen ships its own Analytics + AI and reporting surface. Integration with external ALM tooling is possible via the published API endpoints — we walk through the integration on a call.
Can LoadGen run in CI/CD pipelines like Silk Performer?
Yes. LoadGen supports CI/CD integration: test runs trigger from pipeline stages, results gate the deploy on per-step latency / error / p95 thresholds, and Analytics + AI flags regressions per release.
