Database Benchmark: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Stefan (Diskussion | Beiträge) KKeine Bearbeitungszusammenfassung |
Stefan (Diskussion | Beiträge) |
||
| Zeile 14: | Zeile 14: | ||
Existing DB-Benchmarks: | Existing DB-Benchmarks: | ||
* TPC-C for OLTP benchmarks. | * TPC-C for OLTP benchmarks [https://en.wikipedia.org/wiki/Transaction_Processing_Performance_Council]. | ||
* TPC-R & TPC-H (formerly TPC-DS) for data warehouse & decision support systems. | ** TPC-R & TPC-H (formerly TPC-DS) for data warehouse & decision support systems. | ||
* TPC-W benchmark for Web-based systems. | ** TPC-W benchmark for Web-based systems. | ||
* "The Engineering Database Benchmark". | * "The Engineering Database Benchmark" [http://research.microsoft.com/en-us/um/people/gray/benchmarkhandbook/chapter7.pdf]. | ||
* Open Source Database Benchmark | * "Open Source Database Benchmark" [http://osdb.sourceforge.net/]. | ||
* PolePosition open source database benchmark [http://www.polepos.org/] | * PolePosition open source database benchmark [http://www.polepos.org/]. | ||
== Guidelines == | == Guidelines == | ||
Aktuelle Version vom 15. September 2015, 23:44 Uhr
Synonym: Database Contest.
See also: "Performance-Vergleich von PostgreSQL, SQLite, db4o und MongoDB" Seminar Database Systems Autumn 2011/2012, Master of Science in Engineering, HSR.
Spatial Database Benchmarks
- HSR Texas Geo Database Benchmark
- Comparing PostGIS, SpatiaLite and Geocouch
- Comparing PostGIS with Lucene/Solr Seminar Database Systems Autumn 2013/2014, Master of Science in Engineering, HSR.
- Spatial Overlay/Clipping:
About Database Performance Benchmarking
Existing DB-Benchmarks:
- TPC-C for OLTP benchmarks [3].
- TPC-R & TPC-H (formerly TPC-DS) for data warehouse & decision support systems.
- TPC-W benchmark for Web-based systems.
- "The Engineering Database Benchmark" [4].
- "Open Source Database Benchmark" [5].
- PolePosition open source database benchmark [6].
Guidelines
A database performance benchmark hast to consider following different aspects:
- Cold and warm start (beware that in case of warm start chaching will take place!).
- Equality and Range Queries.
- Query-Result Sets, which respond with one tupel or which respond more than half of the tupels in the dataset.
- Single User versus Multi-user.
Software (Scritps) for benchmark automation:
- PostgreSQL hstore Benchmark - Benchmarking in Python by Michel Ott, 2011.
- pgbench - Benchmark tool for PostgreSQL.
Weblinks / References
- "The Engineering Database Benchmark", Rick Cattell, PDF.
- Open Source Database Benchmark
- http://www.delicious.com/sfkeller/database+benchmark and http://www.delicious.com/tag/database,benchmark/alltime