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 postgresql.

Min sample
55.7 ms
Mean sample
167 ms
Max sample
447 ms
Cumulative time
13.038s
Throughput
5.982/s

Runtime comparison

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

Cycle 2.16.0

cycle/database · mean 60.9 ms · 6 samples

  • postgresql 60.9 ms

Atlas 2.0.1

atlas/pdo · mean 87.1 ms · 6 samples

  • postgresql 87.1 ms

Propel2 6cb272b6

propel/propel · mean 110 ms · 6 samples

  • postgresql 110 ms

PHPFUIBatch 3.0.3

phpfui/orm · mean 113 ms · 6 samples

  • postgresql 113 ms

PHPFUI 3.0.3

phpfui/orm · mean 114 ms · 6 samples

  • postgresql 114 ms

Doctrine 3.6.2

doctrine/orm · mean 142 ms · 6 samples

  • postgresql 142 ms

ActiveRecord 2.0.6

php-patterns/activerecord · mean 145 ms · 6 samples

  • postgresql 145 ms

DivergenceV3 3.2.0

divergence/divergence · mean 165 ms · 6 samples

  • postgresql 165 ms

Yii 2.0.54

yiisoft/yii2 · mean 176 ms · 6 samples

  • postgresql 176 ms

CakeCached 5.3.3

cakephp/cakephp · mean 239 ms · 6 samples

  • postgresql 239 ms

Cake 5.3.3

cakephp/cakephp · mean 241 ms · 6 samples

  • postgresql 241 ms

RedBean 5.7.5

gabordemooij/redbean · mean 274 ms · 6 samples

  • postgresql 274 ms

Eloquent 13.2.0

illuminate/database · mean 307 ms · 6 samples

  • postgresql 307 ms

Where the time goes

Each bar is one framework's mean scenario run on postgresql, 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 15% Insert 16% Read 14% Update 50%

postgresql

  1. Cycle2.16.0 60.9 ms
  2. Atlas2.0.1 87.1 ms
  3. Propel26cb272b6 110 ms
  4. PHPFUIBatch3.0.3 113 ms
  5. PHPFUI3.0.3 114 ms
  6. Doctrine3.6.2 142 ms
  7. ActiveRecord2.0.6 145 ms
  8. DivergenceV33.2.0 165 ms
  9. Yii2.0.54 176 ms
  10. CakeCached5.3.3 239 ms
  11. Cake5.3.3 241 ms
  12. RedBean5.7.5 274 ms
  13. Eloquent13.2.0 307 ms
Exact numbers
Cycle 2.16.0 postgresql 6 60.9 ms 5.19 ms 9.49 ms 26.6 ms 4.47 ms
Atlas 2.0.1 postgresql 6 87.1 ms 6.56 ms 18.2 ms 47.3 ms 7.39 ms
Propel2 6cb272b6 postgresql 6 110 ms 14.2 ms 14.9 ms 55.3 ms 13.1 ms
PHPFUIBatch 3.0.3 postgresql 6 113 ms 7.87 ms 20.7 ms 70.1 ms 5.21 ms
PHPFUI 3.0.3 postgresql 6 114 ms 9.54 ms 21.0 ms 67.0 ms 8.44 ms
Doctrine 3.6.2 postgresql 6 142 ms 26.7 ms 25.5 ms 40.8 ms 5.01 ms
ActiveRecord 2.0.6 postgresql 6 145 ms 20.5 ms 26.8 ms 83.9 ms 4.41 ms
DivergenceV3 3.2.0 postgresql 6 165 ms 19.8 ms 32.6 ms 94.9 ms 8.40 ms
Yii 2.0.54 postgresql 6 176 ms 26.9 ms 34.3 ms 85.5 ms 13.1 ms
CakeCached 5.3.3 postgresql 6 239 ms 73.3 ms 36.6 ms 108 ms 7.35 ms
Cake 5.3.3 postgresql 6 241 ms 68.3 ms 38.3 ms 112 ms 7.68 ms
RedBean 5.7.5 postgresql 6 274 ms 39.3 ms 9.84 ms 195 ms 12.1 ms
Eloquent 13.2.0 postgresql 6 307 ms 46.7 ms 41.4 ms 155 ms 17.0 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.