From 704703b9331a763142f7c1492f5ee161375ac1ec Mon Sep 17 00:00:00 2001 From: brettwooldridge Date: Mon, 21 Oct 2013 15:38:36 +0900 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index acbb22a2..fee67712 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ ![](https://raw.github.com/wiki/brettwooldridge/HikariCP/Hikari.png) HikariCP Ultimate JDBC Connection Pool [![Build Status](https://travis-ci.org/brettwooldridge/HikariCP.png?branch=master)](https://travis-ci.org/brettwooldridge/HikariCP) ========== -There is nothing [faster](https://github.com/brettwooldridge/HikariCP/wiki/How-we-do-it).1 There is +There is nothing [faster](https://github.com/brettwooldridge/HikariCP/wiki/Benchmarks).1 There is nothing more [correct](https://github.com/brettwooldridge/HikariCP/wiki/Correctness). HikariCP is a "zero-overhead" production-quality connection pool. @@ -15,7 +15,7 @@ were performed in ***8ms*** on a commodity PC. The next fastest connection pool 1We contend HikariCP is near the theoretical maximum on current JVM technology.
2400 threads, 50 connection pool. Measurements taken in *nanoseconds* and converted to *milliseconds*. -See benchmarks [here](https://github.com/brettwooldridge/HikariCP/wiki/How-we-do-it)
+See benchmarks [here](https://github.com/brettwooldridge/HikariCP/wiki/Benchmarks)
------------------------------