PostgreSQL各个版本的性能

最新推荐文章于 2025-11-05 22:05:04 发布

原创最新推荐文章于 2025-11-05 22:05:04 发布 · 1.2w 阅读

2 ·

CC 4.0 BY-SA版权

数据库专栏收录该内容

289 篇文章

订阅专栏

从PostgreSQL 7.4到9.4，性能提升了近8倍。9.2版本在此特定测试中的性能与9.3和9.4几乎相同。文章还详细介绍了如何选择基准测试中的scale参数来模拟不同规模的数据库。

原文参见: http://blog.pgaddict.com/posts/performance-since-postgresql-7-4-to-9-4-pgbench

基本结论: PostgreSQL性能, 从7.4分到9.4, 提升近8倍. 9.3 and 9.4 give almost the same performance as 9.2 in this particular test, so only 9.2 is on the chart. PostgreSQL各个版本的性能 - 那海蓝蓝 - 那海蓝蓝的博客

另外,这篇文章中值得注意的有:

Scale

In short, scale determines size of the database as a number of rows in the main "accounts" table - the supplied value gets multiplied by 100.000 and that's how many rows in that table you get. This of course determines the size on disk, as every 100.000 rows corresponds to 15MB on disk (including indexes etc.).

When choosing the scale for your benchmark, you have three basic choices, each testing something slightly different.

small
usually scale between 1-10 (15-150MB databases)
only a small fraction of RAM (assuming regular hardware)
usually exposes locking contention, problems with CPU caches and similar issues not visible with larger scales (where it gets overshadowed by other kinds of overhead - most often I/O)
medium
scales corresponding to ~50% of RAM (e.g. 200-300 on systems with 8GB RAM)
the database fits into RAM (assuming there's enough free memory for queries)
often exposes issues with CPU utilization (especially on read-only workloads) or locking
large
scales corresponding to ~200% of RAM, or more (so 1000 on systems with 8GB RAM)
the database does not fit into RAM, so both modes (read-only and read-write) hit the I/O subsystem
exposes issues with inefficient disk access (e.g. because of missing index) and I/O bottlenecks