Elastic public-cloud generators across regions
Core PE spins load from AWS, Azure, or GCP regions on demand. Programs do not own or maintain generator infrastructure for peak tests.
OpenText • Performance testing
Core Performance Engineering is the SaaS edition of the LoadRunner family, with cloud-hosted load generators, enterprise protocol coverage and CI-ready reporting. The performance program around it, from user journeys to CI gates, is built with Merito.
Core PE scenarios from Merito are modeled on real user journeys, correlated with Dynatrace, New Relic, AppDynamics or Datadog, and run as CI/CD performance gates on right-sized cloud generators.
What it is
OpenText Core Performance Engineering is the SaaS edition of the LoadRunner family. It provides cloud-hosted load generators across public regions, enterprise protocol coverage (web, API, Citrix, Oracle Forms, SAP GUI, WebSocket), and reporting integrated with Application Performance Monitoring tools.
The choice between Core (SaaS), Professional (desktop), and Enterprise (centralized on-prem) is almost entirely about where the team needs load generators to come from and who owns the performance program. Core PE is correct when load needs come from public cloud regions, when elastic scale matters more than fixed capacity, and when performance is part of release-pipeline gating.
Performance engineering lives or dies by scenario design. Tests that represent real user behavior and real peak-event traffic patterns produce actionable results. Tests scripted from documentation produce charts. Merito's engagements start with user-journey analysis and APM-correlated baselines before scripting.
Ideal use cases
What it is best at
Core PE spins load from AWS, Azure, or GCP regions on demand. Programs do not own or maintain generator infrastructure for peak tests.
Scripts and protocols are consistent across Core, Professional, and Enterprise editions, so programs can mix editions without rewriting scripts.
JUnit-compatible reporting and REST-triggerable runs make Core PE a first-class citizen in modern CI pipelines, not a side-of-desk activity.
Core capabilities
Enterprise protocols carried from the LoadRunner family, with cloud-first scripting ergonomics.
Enterprise protocols
Web (HTTP/HTTPS), REST and SOAP APIs, Citrix, Oracle Forms, SAP GUI, WebSocket, and dozens more.
DevWeb and cloud-first scripting
Modern TruClient and DevWeb scripting for cloud-era applications alongside traditional VuGen for legacy protocols.
Open-source friendly
JMeter and Gatling scripts execute inside Core PE for programs standardizing on open-source scripting.
Cloud-hosted generators scale to peak-event volumes without dedicated infrastructure.
Multi-region generators
Load originated from AWS, Azure, or GCP regions globally.
Elastic concurrency
Scale to tens or hundreds of thousands of virtual users on demand for peak tests.
On-prem generators for hybrid scope
Optional on-prem generators for intranet or restricted-network application coverage.
Results integrated with APM, Core SDP, and CI/CD pipelines for actionable analysis.
APM correlation
Dynatrace, New Relic, AppDynamics, and Datadog correlation so performance regressions tie to code and infrastructure changes.
CI/CD gating
REST-triggerable runs and JUnit-compatible reporting for Jenkins, Azure DevOps, GitHub Actions, GitLab CI.
Core SDP and AQM reporting
Performance signals rolled into Core Software Delivery Platform dashboards and AQM evidence for regulated programs.
Where it fits in the stack
Deployment and implementation
Licensing and packaging
Core PE standard
SaaS load generation with multi-region generators and APM correlation.
Best for: Programs moving performance to SaaS with elastic peak scope.
Core PE with Service Virtualization
Standard plus Service Virtualization for dependency-constrained load testing.
Best for: Programs where backend dependencies block load test completeness.
Merito services
Pick the engagement that matches where you are in the lifecycle.
User journey modeling, scenario design, APM correlation, and CI/CD integration.
Explore serviceSAP GUI, Fiori, and S/4HANA performance with SAP-aligned user models.
Explore solutionLoadRunner Cloud to Core Performance Engineering transitions, and moves from on-prem LoadRunner to SaaS.
Explore serviceNamed engineer, priority SLAs, and release-time coverage for Core PE in production.
Explore serviceLong-term run support including peak-event rehearsals and scenario maintenance.
Explore serviceRole-based training for performance engineers, SREs, and release managers.
Explore serviceCore PE licensing
Tests built from real user journeys and APM-correlated baselines produce actionable results, and tests scripted from documentation produce charts.
Merito point of view
Aggressive VU-hour tiers plus generic load scripts produce charts that do not match real peak behavior. The license is not the constraint, the scenario design is. That is why Core PE engagements start with user-journey analysis, APM-correlated baselines and peak-event profiles before any scripting happens.
Core PE, Professional, and Enterprise editions share protocols. Choice between them is about where generators come from and how the performance program is organized. Merito's guidance and Core PE for cloud-first programs, Professional for engineer-led local testing, Enterprise for centralized on-prem capacity with multi-team ownership. Hybrid programs mix all three.
Performance gating in CI is worthwhile only when scenarios are maintained as a first-class asset. A gate that references a stale scenario is worse than no gate. Merito includes scenario ownership rules in the rollout so gates stay meaningful.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share the user journeys and peak-event scope you need to cover. A Merito performance specialist follows up within one business day.
SaaS elasticity
Core PE scales from AWS, Azure, and GCP regions on demand so peak-event capacity is not a hardware problem.
Scenarios matter
Merito's engagements start with user-journey modeling and APM correlation, not VU-hour targets.
Next step
A Merito Core PE engagement starts with the user journeys and APM baselines that matter, not with a scripting template.