MySQL, PostgreSQL和Derby的性能比較

MySQL

PostgreSQL

Derby

性能比較

最近在網上有這樣一種性能對比:

如下是引用的內容:(我的認爲,主要是說明這三種數據庫更適合在哪方面的應用.在大吞吐量的數據傳送Derby是頗有優點的.)不過要注意,Derby的默認緩存只有4M,必定要改到200M以上纔好用.

Performance Evaluation:
MySQL, PostgreSQL and Derby
Evaluated performance of:
? MySQL/InnoDB (version 5.0.10)
? PostgreSQL (version 8.0.3)
? Derby Embedded (version 10.1.1.0)
? Derby Client-Server

Database Configurations
Configurations:
? 「Out-of-box」 performance
? No tuning, except:
> size of database buffer
> database and transaction
log on separate disks
? No Benchmark
Load:
> 1-100 concurrent clients
Databases:
1. Main-memory database:
> 10 MB user data
> 64 MB database buffer
2. Disk database:
> 10 GB user data
> 64 MB database buffer

Throughput: TPC-B like load
Main-memory database (10 MB):               Disk-based database (10 GB):

Observations
? Derby outperforms MySQL on disk-based databases
> Derby has 100% higher throughput than MySQL
? MySQL performs better on small main-memory
databases
> Update-intensive load: Derby has 20-50% lower
throughput
> Read-intensive load: Derby has 50% lower throughput
? PostgreSQL performs best on read-only databases, and
has lowest throughput on update-intensive databases
Why?

Conclusions: Resource Usage? MySQL performs better than Derby when> The database is small and fits in the database buffer> Throughput becomes CPU-bound> Derby uses more CPU and sends more messages over the net? Derby performs better than MySQL when> The database is large and does not fit in the database buffer> Throughput becomes I/O-bound? PosgreSQL performs best with read-only load> Update-intensive load results in much disk I/O