Hikaricp Benchmark

JHM benchmarks for JDBC Connection Pools
Alternatives To Hikaricp Benchmark
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Mango9131422 years ago37July 14, 202024apache-2.0Java
Distributed ORM Framework for Java
Hikaricp Benchmark137
2 years ago18Java
JHM benchmarks for JDBC Connection Pools
7 years ago1Java
Java implementation of TPC-C benchmark
Activiti Benchmark21
8 years agoJava
Shardingsphere Benchmark17
2 years ago1Java
Distributed database middleware
Mango Benchmark15
7 years agoJava
JHM benchmarks for ORM Frameworks
a year ago8May 25, 20192apache-2.0Java
Database persistence layer tool based auto-gen JDBC code
Dbms Benchmarker10115 days ago16June 29, 202220agpl-3.0HTML
DBMS-Benchmarker is a Python-based application-level blackbox benchmark tool for Database Management Systems (DBMS). It connects to a given list of DBMS (via JDBC) and runs a given list of parametrized and randomized (SQL) benchmark queries. Evaluations are available via a Python interface and on an interactive multi-dimensional dashboard.
3 years ago2Java
BenchmarkSQL PostgreSQL TPC-C fair-use implementation (unmaintained, new maintainers welcome)
Sql Benchmark4
4 years agoapache-2.0Ada
Tool to make SQL benchmark on different drivers, languages and databases
Alternatives To Hikaricp Benchmark
Select To Compare

Alternative Project Comparisons

Dependency Status

ConnectionCycle measures cycles of DataSource.getConnection()/Connection.close(). StatementCycle measures cycles of Connection.prepareStatement(), Statement.execute(), Statement.close().

JMH Connection Pool Microbenchmarks

This set of microbenchmaks was developed to refine the HikariCP JDBC connection pool implementation, but it actually runs the same benchmarks across multiple pools.

We have come to understand that benchmarking on the JVM, which employs Dead Code Elimination (DCE), lock-coalescing, inlining, loop-unrolling, on-stack replacement (OSR) and a myriad of other tricks, renders most attempts at benchmarking completely invalid -- including our own original benchmarks. Read all the things that [even smart] people get wrong about benchmarking on the JVM.

The Oracle JVM performance team, primarily Aleksey Shipilёv, developed a microbenchmarking framework called JMH. It provides the infrastructure (if used properly) for accurate comparative measurement of JVM-based execution. If you are interested in microbenchmarking at all, or just curious about all the wonderful things the JVM does, I highly recommend reading this slideshare.

How to run?

  • git clone https://github.com/brettwooldridge/HikariCP-benchmark.git
  • cd HikariCP-benchmark
  • mvn clean package
  • ./benchmark.sh

The benchmark.sh script is a wrapper around JMH execution. A full run of the benchmark will take about 45 minutes for all pools.

There are several more options you can provide to the benchmark.sh. There are a lot actually, but these are most useful...

Specify Shorter Runs
There are two options provided by the script: quick and medium. quick will take about 5 minutes to run, medium will take about 20 minutes -- for all pools. It is extrememly boring to watch, and you can't do anything else on the PC where the benchmark is running without affecting the results, so have dinner, run some errands, etc.

./benchmark.sh quick

If specified with other options, quick or medium must be the first option.

Specify Specific Pools

./benchmark.sh -p pool=hikari,bone

Where pool is a comma-separated list (hikari, dbcp2, tomcat, c3p0, vibur). Specifying a specific pool or subset of pools will shorten run times.

Specify Pool Size

./benchmark.sh -p maxPoolSize=16

Pool size is only applicable for the Connection Cycle test, attempting to run the Statement Cycle test with a pool smaller than the number of threads (8) will result in testing failures. The Connection Cycle test runs with 8 threads, so to test a contrained pool condition set maxPoolSize to a smaller number (eg. 4).

Specify which Benchmark
There are two benchmarks in the suite currently: ConnectionBench and StatementBench. By default both benchmarks are run, but if you want to run one or the other you can use a JMH option using a regex (regular experession) to do so. For example, to only run the StatementBench use:

./benchmark.sh ".*Statement.*"

All of the options can be combined:

./benchmark.sh medium -p pool=hikari,vibur -p maxPoolSize=4 ".*Connection.*"

Popular Jdbc Projects
Popular Benchmark Projects
Popular Data Processing Categories

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.