diff --git a/README.md b/README.md index 01042dd6..6e3979e2 100644 --- a/README.md +++ b/README.md @@ -1,27 +1,30 @@ ![](https://raw.github.com/wiki/brettwooldridge/HikariCP/Hikari.png) HikariCP It's Faster. [![Build Status](https://travis-ci.org/brettwooldridge/HikariCP.png?branch=master)](https://travis-ci.org/brettwooldridge/HikariCP)[![](https://raw.github.com/wiki/brettwooldridge/HikariCP/twitter.png)](https://twitter.com/share?text=Interesting%20JDBC%20Connection%20Pool&hashtags=HikariCP&url=https%3A%2F%2Fgithub.com%2Fbrettwooldridge%2FHikariCP) [![](https://raw.github.com/wiki/brettwooldridge/HikariCP/facebook.png)](http://www.facebook.com/plugins/like.php?href=https%3A%2F%2Fgithub.com%2Fbrettwooldridge%2FHikariCP&width&layout=standard&action=recommend&show_faces=true&share=false&height=80) ========== -There is nothing [faster](https://github.com/brettwooldridge/HikariCP/wiki/Benchmarks).1 There is +There is nothing [faster](https://github.com/brettwooldridge/HikariCP/wiki/Benchmarks). There is nothing more [correct](https://github.com/brettwooldridge/HikariCP/wiki/Correctness). HikariCP is a "zero-overhead" production-quality connection pool. Coming in at roughly 50Kb, the library is extremely light. -Using a stub-JDBC implementation to isolate and measure the overhead of HikariCP, 60+ Million JDBC operations -were performed in ***10ms*** on a commodity PC.2  The next fastest connection pool ([Tomcat](http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html)) was ***1874ms***. Apache DBCP and C3P0 failed to successfully execute the benchmark. +Using a stub-JDBC implementation to isolate and measure the overhead of HikariCP comparative benchmarks were performed +on a commodity PC.2  The next fastest connection pool was [BoneCP](http://jolbox.com). + +Sample from benchmark, 50 connection pool, 200 threads: | Pool | Med (ms) | Avg (ms) | Max (ms) | | -------- | ---------:| ---------:| ---------:| -| BoneCP | 4635 | 3060 | 6747 | -| Tomcat | 1874 | 1719 | 1882 | -| HikariCP | 10 | 9 | 13 | - -1We contend HikariCP is near the theoretical maximum on current JVM technology.
-2400 threads, 50 connection pool. Measurements in *nanoseconds* and converted to *milliseconds*. -See benchmarks [here](https://github.com/brettwooldridge/HikariCP/wiki/Benchmarks). See how we do it [here](https://github.com/brettwooldridge/HikariCP/wiki/Down-the-Rabbit-Hole).
-3Benchmark numbers updated periodically to reflect latest developments.
+| HikariCP | 15829 | 15898 | 15992 | +| BoneCP | 20370 | 20424 | 20630 | +| Tomcat | 55763 | 55750 | 55818 | +| C3P0 | 1874414 | 1869412 | 1881736 | Or look at this: ![](http://github.com/brettwooldridge/HikariCP/wiki/50Connection_MixedBench.png) +150 connection pool. Measurements in *nanoseconds* and converted to *milliseconds*. +See benchmarks [here](https://github.com/brettwooldridge/HikariCP/wiki/Benchmarks). See how we do it [here](https://github.com/brettwooldridge/HikariCP/wiki/Down-the-Rabbit-Hole).
+2Tomcat and C3P0 omitted from chart for scale.
+3Benchmark numbers updated periodically to reflect latest developments.
+ ---------------------------------------------------- ### Maven Repository ### ```xml