开源软件名称：

开源软件地址：

开源软件介绍：

HikariCP ^{It's Faster._{Hi·ka·ri [hi·ka·'lē] (Origin: Japanese): light; ray.}}

Fast, simple, reliable. HikariCP is a "zero-overhead" production ready JDBC connection pool. At roughly 130Kb, the library is very light. Read about how we do it here.

   ^{"Simplicity is prerequisite for reliability."
         - Edsger Dijkstra}

Index

• Artifacts
• JMH Benchmarks
• Analyses
  • Spike Demand Pool Comparison
  • You're probably doing it wrong
  • WIX Engineering Analysis
  • Failure: Pools behaving badly
• User Testimonials
  
• Configuration
  
  • Essentials
  • Frequently used
  • Infrequently used
• Initialization

Artifacts

Java 11+ maven artifact:

<dependency>   <groupId>com.zaxxer</groupId>   <artifactId>HikariCP</artifactId>   <version>5.0.1</version></dependency>

Java 8 maven artifact (maintenance mode):

<dependency>   <groupId>com.zaxxer</groupId>   <artifactId>HikariCP</artifactId>   <version>4.0.3</version></dependency>

Java 7 maven artifact (maintenance mode):

<dependency>   <groupId>com.zaxxer</groupId>   <artifactId>HikariCP-java7</artifactId>   <version>2.4.13</version></dependency>

Java 6 maven artifact (maintenance mode):

<dependency>   <groupId>com.zaxxer</groupId>   <artifactId>HikariCP-java6</artifactId>   <version>2.3.13</version></dependency>

Or download from here.

JMH Benchmarks

Microbenchmarks were created to isolate and measure the overhead of pools using the JMH microbenchmark framework. You can checkout the HikariCP benchmark project for details and review/run the benchmarks yourself.

• One Connection Cycle is defined as single DataSource.getConnection()/Connection.close().
• One Statement Cycle is defined as single Connection.prepareStatement(), Statement.execute(), Statement.close().

Analyses

Spike Demand Pool Comparison

Analysis of HikariCP v2.6, in comparison to other pools, in relation to a unique "spike demand" load.

The customer's environment imposed a high cost of new connection acquisition, and a requirement for a dynamically-sized pool, but yet a need for responsiveness to request spikes. Read about the spike demand handling here.

You're [probably] doing it wrong

AKA "What you probably didn't know about connection pool sizing". Watch a video from the Oracle Real-world Performance group, and learn about why connection pools do not need to be sized as large as they often are. In fact, oversized connection pools have a clear and demonstrable negative impact on performance; a 50x difference in the case of the Oracle demonstration. Read on to find out.

WIX Engineering Analysis

We'd like to thank the guys over at WIX for the unsolicited and deep write-up about HikariCP on their engineering blog. Take a look if you have time.

Failure: Pools behaving badly

Read our interesting "Database down" pool challenge.

"Imitation Is The Sincerest Form Of Plagiarism" - _^anonymous

Open source software like HikariCP, like any product, competes in the free market. We get it. We understand that product advancements, once public, are often co-opted. And we understand that ideas can arise from the zeitgeist; simultaneously and independently. But the timeline of innovation, particularly in open source projects, is also clear and we want our users to understand the direction of flow of innovation in our space. It could be demoralizing to see the result of hundreds of hours of thought and research co-opted so easily, and perhaps that is inherent in a free marketplace, but we are not demoralized. We are motivated; to widen the gap.

User Testimonials

:gear: Configuration (knobs, baby!)

HikariCP comes with sane defaults that perform well in most deployments without additional tweaking. Every property is optional, except for the "essentials" marked below.