This is a very basic test of PostgreSQL crash recovery time. The numbers it spits out are the time to replay a certain number of transactions, and optionally complete the end-of-recovery checkpoint.
Here are some numbers from a developer system. Real life performance depends on many factors, so of course your mileage may vary a lot, ... The numbers reported here are the time from redo beginning to the end-of-recovery checkpoint completing (that is, the two numbers printed out by crash-recover.sh added together), replaying 8 million transactions with full page writes on. Test were run 4 times each, and avg and stddev are shown; speed-up is computed with student's T at 95% confidence.
| Branch | Avg | Stddev | Speed-up | Explanation |
|---|---|---|---|---|
| REL_11_STABLE | 92.3s | 3.0s | ||
| REL_12_STABLE | 84.0s | 2.2s | 9% faster than 11 (+/- 5.4%) | Commit Commit |
| REL_13_STABLE | 84.6s | 3.0s | no difference | |
| master | 60.2s | 1.8s | 40% faster than 13 (+/- 7%) | Commit |
| slru-offload-fsync | 55.5s | 0.4s | 52% faster than 13 (+/- 6.6%), 9% faster than master (+/- 4.0%) | Proposal |
| fast-compactify-tuples | 49.5s | 0.6s | 71% faster than 13 (+/- 7.5%), 12% faster than slru-offload-fsync (+/- 1.6%) | Proposal |