HikariCP JDBC连接池 v5.1.0.zip

<h1><img src="https://github.com/brettwooldridge/HikariCP/wiki/Hikari.png"> HikariCP^{^{&nbsp;It's Faster.}}_{_{^{Hi·ka·ri [hi·ka·'lē] &#40;<i>Origin: Japanese</i>): light; ray.}}}</h1><br> [![][Build Status img]][Build Status] [![][Coverage Status img]][Coverage Status] [![][license img]][license] [![][Maven Central img]][Maven Central] [![][Javadocs img]][Javadocs] [![][Librapay img]][Librapay] 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](https://github.com/brettwooldridge/HikariCP/wiki/Down-the-Rabbit-Hole). &nbsp;&nbsp;&nbsp;^{**"Simplicity is prerequisite for reliability."**<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- *Edsger Dijkstra*} ---------------------------------------------------- ### Index * [Artifacts](#artifacts) * [JMH Benchmarks](#checkered_flag-jmh-benchmarks) * [Analyses](#microscope-analyses) * [Spike Demand Pool Comparison](#spike-demand-pool-comparison) * [You're probably doing it wrong](#youre-probably-doing-it-wrong) * [WIX Engineering Analysis](#wix-engineering-analysis) * [Failure: Pools behaving badly](#failure-pools-behaving-badly) * [User Testimonials](#family-user-testimonials) <br> * [Configuration](#gear-configuration-knobs-baby) <br> * [Essentials](#essentials) * [Frequently used](#frequently-used) * [Infrequently used](#infrequently-used) * [Initialization](#rocket-initialization) ---------------------------------------------------- ### Artifacts _**Java 11+** maven artifact:_ ```xml <dependency> <groupId>com.zaxxer</groupId> <artifactId>HikariCP</artifactId> <version>5.0.1</version> </dependency> ``` _Java 8 maven artifact (*maintenance mode*):_ ```xml <dependency> <groupId>com.zaxxer</groupId> <artifactId>HikariCP</artifactId> <version>4.0.3</version> </dependency> ``` _Java 7 maven artifact (*maintenance mode*):_ ```xml <dependency> <groupId>com.zaxxer</groupId> <artifactId>HikariCP-java7</artifactId> <version>2.4.13</version> </dependency> ``` _Java 6 maven artifact (*maintenance mode*):_ ```xml <dependency> <groupId>com.zaxxer</groupId> <artifactId>HikariCP-java6</artifactId> <version>2.3.13</version> </dependency> ``` Or [download from here](http://search.maven.org/#search%7Cga%7C1%7Ccom.zaxxer.hikaricp). ---------------------------------------------------- ### :checkered_flag: JMH Benchmarks Microbenchmarks were created to isolate and measure the overhead of pools using the [JMH microbenchmark framework](http://openjdk.java.net/projects/code-tools/jmh/). You can checkout the [HikariCP benchmark project for details](https://github.com/brettwooldridge/HikariCP-benchmark) 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()``. ^{¹ Versions: HikariCP 2.6.0, commons-dbcp2 2.1.1, Tomcat 8.0.24, Vibur 16.1, c3p0 0.9.5.2, Java 8u111 <br/> ² Intel Core i7-3770 CPU @ 3.40GHz <br/> ³ Uncontended benchmark: 32 threads/32 connections, Contended benchmark: 32 threads, 16 connections <br/> ⁴ Apache Tomcat fails to complete the Statement benchmark when the Tomcat <i>StatementFinalizer</i> is used <a href="https://raw.githubusercontent.com/wiki/brettwooldridge/HikariCP/markdown/Tomcat-Statement-Failure.md">due to excessive garbage collection times</a><br/> ⁵ Apache DBCP fails to complete the Statement benchmark <a href="https://raw.githubusercontent.com/wiki/brettwooldridge/HikariCP/markdown/Dbcp2-Statement-Failure.md">due to excessive garbage collection times</a>} ---------------------------------------------------- ### :microscope: Analyses #### Spike Demand Pool Comparison <a href="https://github.com/brettwooldridge/HikariCP/blob/dev/documents/Welcome-To-The-Jungle.md"><img width="400" align="right" src="https://github.com/brettwooldridge/HikariCP/wiki/Spike-Hikari.png"></a> 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](https://github.com/brettwooldridge/HikariCP/blob/dev/documents/Welcome-To-The-Jungle.md). <br/> <br/> #### You're [probably] doing it wrong <a href="https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing"><img width="200" align="right" src="https://github.com/brettwooldridge/HikariCP/wiki/Postgres_Chart.png"></a> 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](https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing). <br/> #### WIX Engineering Analysis <a href="https://www.wix.engineering/blog/how-does-hikaricp-compare-to-other-connection-pools"><img width="180" align="left" src="https://github.com/brettwooldridge/HikariCP/wiki/Wix-Engineering.png"></a> We'd like to thank the guys over at WIX for the unsolicited and deep write-up about HikariCP on their [engineering blog](https://www.wix.engineering/post/how-does-hikaricp-compare-to-other-connection-pools). Take a look if you have time. <br/> <br/> <br/> #### Failure: Pools behaving badly Read our interesting ["Database down" pool challenge](https://github.com/brettwooldridge/HikariCP/wiki/Bad-Behavior:-Handling-Database-Down). ---------------------------------------------------- #### "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.* ---------------------------------------------------- ### :family: User Testimonials [](https://twitter.com/jkuipers)<br/> [](https://twitter.com/steve_objectify)<br/> [](https://twitter.com/brettemeyer)<br/> [](https://twitter.com/dgomesbr/status/527521925401419776) ------------------------------ ### :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.** ^&#128206;&nbsp;*HikariCP uses milliseconds for all time values.* &#128680;&nbsp;HikariCP relies on accurate timers for both performance and reliability. It is *imperative* that your server is synchronized with a time-source such as an NTP server. *Especially* if your server is running within a virtual machine. Why? [Rea