PERFORMANCE METHODOLOGY

Measure your application, not a headline.

Review compatibility, isolation, resource policy, deployment identity, and recovery requirements with explicit criteria.

Use requirements you can verify

No comparative benchmark is published here. A useful test records the application revision, PHP version, engine mode, dataset, concurrency, latency distribution, throughput, CPU, and memory under identical conditions.

1. Freeze a representative workload

Record the application commit, dependency lockfile, dataset, PHP version, enabled extensions, cache state, and runtime mode. Use the same machine resources, request mix, and external services for every engine.

Include the work users actually perform: an uncached page, authenticated requests, database queries, and any write-heavy path. A hello-world result does not describe the application as a whole.

2. Measure latency and resource use together

Warm the application consistently, then increase concurrency in controlled steps. Record duration, error rate, throughput, median latency, p95 and p99 latency, CPU, memory, and process pressure. Mark timeouts and failed responses as failures.

Keep cold-start behaviour separate from warm steady-state results. For long-lived workers, also observe memory growth and state leakage over repeated requests.

3. Publish conditions alongside the result

Preserve the raw measurements, test configuration, sample size, and timestamp. Explain which configuration changed and whether all functional checks passed. Do not turn a single endpoint result into a claim that every PHP application is faster.

No comparative benchmark or percentage improvement is currently published for Orisite. Runtime selection should begin with compatibility and then be measured against a repeatable baseline.

A reproducible benchmark record
EvidenceRecord
ApplicationCommit, lockfile, dataset, routes, and request mix
RuntimeEngine, PHP version, extensions, worker or FPM configuration
CapacityCPU, memory, process policy, and host conditions
OutcomeLatency distribution, errors, throughput, and resource observations
YOUR APPLICATION. YOUR WORKFLOW.

Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.