The PHP Bench
All runs

20260329203643-74505162

complete Signed by runner-20260329222123 · 409ffba3dd66...5ffbf106
Started
Generated
Measured samples
78
Combinations
13

Machine

Captured from the runner's system manifest.

Host eimu Linux · kernel 6.19.6
PHP 8.5.3
Processor AMD Ryzen 9 5950X 16-Core Processor 32 cores · x86_64
Memory 31.2 GB DIMM_A2 16 GiB 2666 MT/s DDR4 F4-4266C19-16GVK DIMM_B2 16 GiB 2666 MT/s DDR4 F4-4266C19-16GVK
Disk 3.5 TB Device: /dev/nvme0n1 Capacity: 3.5 TB

Runtime envelope

End-to-end time per scenario run across all non-warmup samples on mariadb.

Min sample
53.7 ms
Mean sample
127 ms
Max sample
409 ms
Cumulative time
9.909s
Throughput
7.872/s

Runtime comparison

Mean time per scenario run in this upload, warmup runs excluded, sorted by runtime.

Init Insert Read Update Delete
  1. Atlas 2.0.1 mariadb 59.1 ms
  2. PHPFUIBatch 3.0.3 mariadb 72.1 ms
  3. Cycle 2.16.0 mariadb 72.9 ms
  4. PHPFUI 3.0.3 mariadb 76.7 ms
  5. Propel2 6cb272b6 mariadb 92.3 ms
  6. DivergenceV2 2.1.4 mariadb 99.3 ms
  7. DivergenceV3 3.2.0 mariadb 117 ms
  8. Yii 2.0.54 mariadb 125 ms
  9. Doctrine 3.6.2 mariadb 146 ms
  10. RedBean 5.7.5 mariadb 149 ms
  11. Cake 5.3.3 mariadb 174 ms
  12. CakeCached 5.3.3 mariadb 177 ms
  13. Eloquent 13.2.0 mariadb 291 ms

Where the time goes

Each bar is one framework's mean scenario run on mariadb, split into its phases and sorted by total. Bars share a scale within each engine. Hover a bar for the numbers.

Init Insert Read Update Delete
Mean split across 13 combinations
Init 20% Insert 16% Read 14% Update 45%

mariadb

  1. Atlas2.0.1 59.1 ms
  2. PHPFUIBatch3.0.3 72.1 ms
  3. Cycle2.16.0 72.9 ms
  4. PHPFUI3.0.3 76.7 ms
  5. Propel26cb272b6 92.3 ms
  6. DivergenceV22.1.4 99.3 ms
  7. DivergenceV33.2.0 117 ms
  8. Yii2.0.54 125 ms
  9. Doctrine3.6.2 146 ms
  10. RedBean5.7.5 149 ms
  11. Cake5.3.3 174 ms
  12. CakeCached5.3.3 177 ms
  13. Eloquent13.2.0 291 ms
Exact numbers
Atlas 2.0.1 mariadb 6 59.1 ms 5.48 ms 11.2 ms 35.0 ms 5.48 ms
PHPFUIBatch 3.0.3 mariadb 6 72.1 ms 7.55 ms 12.3 ms 46.4 ms 3.09 ms
Cycle 2.16.0 mariadb 6 72.9 ms 5.78 ms 11.2 ms 35.6 ms 5.94 ms
PHPFUI 3.0.3 mariadb 6 76.7 ms 8.87 ms 12.6 ms 46.4 ms 6.08 ms
Propel2 6cb272b6 mariadb 6 92.3 ms 14.1 ms 12.7 ms 48.8 ms 9.51 ms
DivergenceV2 2.1.4 mariadb 6 99.3 ms 13.4 ms 16.6 ms 61.4 ms 5.90 ms
DivergenceV3 3.2.0 mariadb 6 117 ms 15.6 ms 22.8 ms 69.8 ms 6.57 ms
Yii 2.0.54 mariadb 6 125 ms 18.6 ms 25.9 ms 60.8 ms 9.57 ms
Doctrine 3.6.2 mariadb 6 146 ms 26.8 ms 26.9 ms 41.3 ms 4.84 ms
RedBean 5.7.5 mariadb 6 149 ms 19.6 ms 7.55 ms 96.4 ms 8.74 ms
Cake 5.3.3 mariadb 6 174 ms 53.2 ms 26.0 ms 76.8 ms 5.65 ms
CakeCached 5.3.3 mariadb 6 177 ms 54.5 ms 26.8 ms 76.6 ms 5.72 ms
Eloquent 13.2.0 mariadb 6 291 ms 46.4 ms 38.6 ms 148 ms 16.5 ms

Scenario families

Mean across every framework and engine in this upload.

  • simple 99.7 ms
  • string_fixed 119 ms
  • string_variable 122 ms
  • int_fixed 124 ms
  • float_fixed 141 ms
  • canary 154 ms

What the workloads measure

The row shape and operation mix decide where each framework spends its time.

Scenario families
simple baseline row shape
Shows framework overhead with minimal field complexity, so object creation and query setup dominate.
canary mixed field and nullable stress
Wide mixed records amplify casting, hydration, dirty tracking, and adapter metadata overhead.
int_fixed pure scalar writes
A low-noise floor. Slow results here usually mean framework machinery is expensive even before text and cast-heavy payloads show up.
float_fixed numeric conversion paths
Decimal and float normalization can widen update and verification cost, especially for ORMs that compare serialized values.
string_fixed predictable text hydration
Column count and text assignment matter more than payload variability, which makes hydration strategy easier to isolate.
string_variable application-like text workload
Variable strings and note fields make this the closest to real CRUD traffic and usually punish heavier active-record layers the most.
Operation shapes
Warmup vs hot runs
Run 1 is warmup. Hot-path averages exclude it so boot and metadata setup do not dominate steady-state rankings.
Insert and indexed schemas
Indexed tables make writes cost more because every insert and many updates must maintain secondary indexes as well as the row itself.
Read all vs read probes
Read All rewards bulk hydration efficiency; random and tail probes expose per-query setup, lookup overhead, and tiny-result inefficiency.
Update with verification
Each update shape is followed by a verification read, so dirty-checking, write SQL generation, hydration, and comparison all affect the final time.
Delete with confirmation
Deletes are checked afterward. Frameworks that pay extra for follow-up lookups or teardown lose more time here than a bare SQL path.
Total runtime
The total runtime metric is effectively a benchmark of the machine plus adapter behavior across the full workload, not just one CRUD verb.