From 78ffed04f061c20291f72e1c6b951ded505e2a98 Mon Sep 17 00:00:00 2001 From: brettwooldridge Date: Thu, 12 Dec 2013 13:33:52 +0900 Subject: [PATCH] Updated chart with Tomcat JDBC pool result. --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7574b0a3..36583cb0 100644 --- a/README.md +++ b/README.md @@ -6,11 +6,12 @@ nothing more [correct](https://github.com/brettwooldridge/HikariCP/wiki/Correctn 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 ***8ms*** on a commodity PC.2 The next fastest connection pool (BoneCP) was ***5298ms***. +were performed in ***8ms*** on a commodity PC.2  The next fastest connection pool ([Tomcat](http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html)) was ***1874ms***. | Pool | Med (ms) | Avg (ms) | Max (ms) | | -------- | ---------:| ---------:| ---------:| -| BoneCP | 5298 | 3249 | 6929 | +| BoneCP | 4635 | 3060 | 6747 | +| Tomcat | 1874 | 1719 | 1882 | | HikariCP | 8 | 7 | 13 | 1We contend HikariCP is near the theoretical maximum on current JVM technology.