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
OpenText Core Performance Engineering
Core Performance Engineering is the SaaS edition of the LoadRunner family and cloud-hosted load generators, enterprise protocol coverage, and CI-ready reporting. Merito builds the performance program.
Merito sells OpenText Core Performance Engineering (LoadRunner Cloud lineage) and delivers SaaS performance testing rollouts and scenario modeling, load-generator provisioning, APM correlation, and CI/CD gating.
- Best for
- Performance Engineering CoEs, SRE and Platform Engineering teams owning performance budgets, Release Managers adding performance gates to CI/CD
- Hosting
- SaaS
- Time to value
- First CI-triggered performance run in as little as one week for narrow scope. First CI-triggered peak test in four to six weeks. Meaningful performance gate coverage across release cycles in three to five months.
- Security posture
- SOC 2 Type II, ISO 27001, GDPR
- Last reviewed
- 2026-04-26
What it is
OpenText Core Performance Engineering in the enterprise stack
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 SDP 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
- Cloud-hosted load generation across multiple public regions
- Peak-event rehearsals (Black Friday, launch day, SAP month-end close)
- CI/CD performance gating on pull request and release
- APM-correlated performance testing with Dynatrace, New Relic, AppDynamics
- SAP and non-SAP performance programs with elastic capacity needs
What it is best at
Where OpenText Core Performance Engineering earns its seat
Shares protocols with Professional and Enterprise
Scripts and protocols are consistent across Core, Professional, and Enterprise editions, so programs can mix editions without rewriting scripts.
CI-native reporting and gating
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
OpenText Core Performance Engineering capabilities, grouped by outcome
Protocol coverage and scripting
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.
Execution and elasticity
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.
Reporting and integration
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
How OpenText Core Performance Engineering connects to the rest of your landscape
APM and observability (native)
Native- Dynatrace, New Relic, AppDynamics, DatadogAPM correlation so performance regressions tie to code and infrastructure changes.
- OpenText Service VirtualizationSimulated service endpoints for dependency-constrained performance tests.
OpenText DevOps catalog (certified)
Certified- OpenText Core Software Delivery PlatformPerformance results in Core SDP dashboards.
- OpenText Application Quality ManagementPerformance evidence linked to regulated QA in AQM.
- OpenText Software Delivery ManagementPerformance signals inside scaled-agile governance.
CI/CD and open-source (custom)
Custom- Jenkins, Azure DevOps, GitHub Actions, GitLab CIREST-triggered runs and CI-friendly reporting.
- JMeter, GatlingOpen-source scripts executed inside Core PE for hybrid scripting programs.
Deployment and implementation
How it rolls out
- Hosting
- SaaS (North America, EMEA, APJ)
- Implementation complexity
- Moderate
- Typical time to value
- First CI-triggered performance run in as little as one week for narrow scope. First CI-triggered peak test in four to six weeks. Meaningful performance gate coverage across release cycles in three to five months.
- Prerequisites
- Named user journeys for performance modeling
- APM tool identified for correlation
- CI pipeline integration plan
- Peak-event scenario requirements (launch day, month-end close)
- What Merito usually handles
- Merito handles Core PE setup, scenario design, APM correlation, CI integration, generator sizing, and team enablement. Performance program ownership typically stays with the customer; for programs that want Merito to run peak rehearsals or day-to-day operations, Managed Services and Staff Augmentation extend the engagement.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- OpenText Core Performance Engineering is subscription-licensed with packaging keyed to virtual-user hours, user seats, and region coverage. Pricing depends on VU-hour tier, concurrent executions, and geographic regions. Merito sells Core PE alongside the performance program design that turns VU hours into business value.
- Editions and modules
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.
- Common expansion areas
- Higher VU-hour tiers for larger peak scenarios
- Service Virtualization for dependency-constrained tests
- Enterprise PE for programs needing centralized on-prem capacity
- Core SDP for test management and consolidation
- Managed Services for ongoing program support
Merito services
How Merito helps you win with OpenText Core Performance Engineering
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
01
Performance Program Design
User journey modeling, scenario design, APM correlation, and CI/CD integration.
Explore service02SAP Performance Testing
SAP GUI, Fiori, and S/4HANA performance with SAP-aligned user models.
Explore solution03DevOps Consulting
Core PE wired into release pipelines for gating.
Explore service04Upgrade and Migration
LoadRunner Cloud to Core Performance Engineering transitions, and moves from on-prem LoadRunner to SaaS.
Explore service05Premium Support
Named engineer, priority SLAs, and release-time coverage for Core PE in production.
Explore service06Managed Services
Long-term run support including peak-event rehearsals and scenario maintenance.
Explore service07Training and Enablement
Role-based training for performance engineers, SREs, and release managers.
Explore service08Staff Augmentation
Merito-placed performance engineers embedded with your team.
Explore serviceCore PE licensing
Buy Core PE from the partner that also designs the scenarios.
Merito sells OpenText Core Performance Engineering and delivers user-journey modeling, APM correlation, CI integration, and peak-event rehearsals that make VU hours matter.
Merito point of view
VU hours are not the success metric. Representative scenarios are.
Merito has seen customers buy aggressive VU-hour tiers, run generic load scripts, and produce charts that do not match real peak behavior. The cost of the license is not the constraint; the scenario design is. Merito's 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
- Buying VU-hour tiers before scenario design is scoped.
- Scripting load tests from documentation instead of user behavior.
- Skipping APM correlation, so regressions have no diagnostic context.
- Running CI performance gates against stale scenarios.
- Treating Core PE as infrastructure rather than part of release governance.
Related from Merito
Continue exploring OpenText Core Performance Engineering on Merito
Related solutions
Related services
Related products
- OpenText Professional Performance EngineeringDesktop edition for engineers running single-user and mid-scale load locally.
- OpenText Enterprise Performance EngineeringCentralized on-prem edition for multi-team performance programs.
- OpenText Service VirtualizationSimulated endpoints for dependency-constrained load testing.
- OpenText DevOps AviatorAI-assisted scenario drafting and result interpretation.
- OpenText (vendor portfolio)OpenText hub and the full DevOps and Content catalogs.
Frequently Asked Questions
OpenText Core Performance Engineering FAQs
Consultation request
Talk to Merito about OpenText Core Performance Engineering
Share the user journeys and peak-event scope you need to cover. A Merito performance specialist follows up within one business day.
SaaS elasticity
Peak events without owning generators
Core PE scales from AWS, Azure, and GCP regions on demand so peak-event capacity is not a hardware problem.
Scenarios matter
VU hours are inputs, not outputs
Merito's engagements start with user-journey modeling and APM correlation, not VU-hour targets.
Next step
Model the journeys. Correlate with APM. Gate in CI.
A Merito Core PE engagement starts with the user journeys and APM baselines that matter, not with a scripting template.