The PHP Bench
All runs

20260928011232-b9eaed5b

complete Signed by kaiju · 9f9bb07dedd6...91a4d3d3
Started
Generated
Measured samples
1,872
Combinations
13

Machine

Captured from the runner's system manifest.

Host kaiju Linux · kernel 6.19.8-200.nobara.fc43.x86_64
PHP 8.5.11
Processor Intel(R) Xeon(R) CPU E5-2687W v4 @ 3.00GHz 48 cores · x86_64
Memory 251.7 GB P1_DIMMA1 32 GB 2133 MT/s DDR4 M386A4G40DM0-CPB P1_DIMMB1 32 GB 2133 MT/s DDR4 M386A4G40DM0-CPB P1_DIMMC1 32 GB 2133 MT/s DDR4 M386A4G40DM0-CPB P1_DIMMD1 32 GB 2133 MT/s DDR4 M386A4G40DM0-CPB P2_DIMME1 32 GB 2133 MT/s DDR4 M386A4G40DM0-CPB P2_DIMMF1 32 GB 2133 MT/s DDR4 M386A4G40DM0-CPB P2_DIMMG1 32 GB 2133 MT/s DDR4 M386A4G40DM0-CPB P2_DIMMH1 32 GB 2133 MT/s DDR4 M386A4G40DM0-CPB
Disk 447.1 GB Device: /dev/sda Capacity: 447.1 GB

Runtime envelope

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

Min sample
35.3 ms
Mean sample
1,719 ms
Max sample
7,905 ms
Cumulative time
53m 38s
Throughput
0.582/s

Runtime comparison

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

Init Insert Read Update Delete
  1. Doctrine 3.6.2 sqlite-file 132 ms
  2. Cake 5.3.3 sqlite-file 315 ms
  3. CakeCached 5.3.3 sqlite-file 317 ms
  4. PHPFUIBatch 3.0.3 sqlite-file 958 ms
  5. ActiveRecord 2.0.6 sqlite-file 1,676 ms
  6. Atlas 2.0.1 sqlite-file 2,237 ms
  7. Cycle 2.16.0 sqlite-file 2,242 ms
  8. PHPFUI 3.0.3 sqlite-file 2,318 ms
  9. Propel2 6cb272b6 sqlite-file 2,318 ms
  10. DivergenceV3 3.2.0 sqlite-file 2,374 ms
  11. Yii 2.0.54 sqlite-file 2,401 ms
  12. RedBean 5.7.5 sqlite-file 2,438 ms
  13. Eloquent 13.2.0 sqlite-file 2,621 ms

Where the time goes

Each bar is one framework's mean scenario run on sqlite-file, 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
Insert 29% Update 43% Delete 25%

sqlite-file

  1. Doctrine3.6.2 132 ms
  2. Cake5.3.3 315 ms
  3. CakeCached5.3.3 317 ms
  4. PHPFUIBatch3.0.3 958 ms
  5. ActiveRecord2.0.6 1,676 ms
  6. Atlas2.0.1 2,237 ms
  7. Cycle2.16.0 2,242 ms
  8. PHPFUI3.0.3 2,318 ms
  9. Propel26cb272b6 2,318 ms
  10. DivergenceV33.2.0 2,374 ms
  11. Yii2.0.54 2,401 ms
  12. RedBean5.7.5 2,438 ms
  13. Eloquent13.2.0 2,621 ms
Exact numbers
Doctrine 3.6.2 sqlite-file 144 132 ms 15.1 ms 25.5 ms 51.3 ms 22.1 ms
Cake 5.3.3 sqlite-file 144 315 ms 76.5 ms 49.6 ms 151 ms 32.4 ms
CakeCached 5.3.3 sqlite-file 144 317 ms 77.2 ms 50.0 ms 152 ms 32.6 ms
PHPFUIBatch 3.0.3 sqlite-file 144 958 ms 12.8 ms 16.6 ms 913 ms 15.1 ms
ActiveRecord 2.0.6 sqlite-file 144 1,676 ms 694 ms 25.5 ms 941 ms 14.5 ms
Atlas 2.0.1 sqlite-file 144 2,237 ms 679 ms 13.0 ms 881 ms 664 ms
Cycle 2.16.0 sqlite-file 144 2,242 ms 688 ms 8.17 ms 875 ms 664 ms
PHPFUI 3.0.3 sqlite-file 144 2,318 ms 705 ms 16.7 ms 915 ms 680 ms
Propel2 6cb272b6 sqlite-file 144 2,318 ms 697 ms 7.84 ms 910 ms 700 ms
DivergenceV3 3.2.0 sqlite-file 144 2,374 ms 711 ms 28.9 ms 956 ms 677 ms
Yii 2.0.54 sqlite-file 144 2,401 ms 703 ms 30.6 ms 952 ms 712 ms
RedBean 5.7.5 sqlite-file 144 2,438 ms 736 ms 23.4 ms 970 ms 702 ms
Eloquent 13.2.0 sqlite-file 144 2,621 ms 743 ms 51.8 ms 1,065 ms 746 ms

Scenario families

Mean across every framework and engine in this upload.

  • simple 178 ms
  • string_variable 1,076 ms
  • string_fixed 1,108 ms
  • float_fixed 1,283 ms
  • int_fixed 1,296 ms
  • canary 1,546 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.