From: fhanik <fhanik@13f79535-47bb-0310-9956-ffa450edef68>
Date: Tue, 21 Jul 2009 16:20:11 +0000 (+0000)
Subject: Document Linux performance/overhead of using multi lock mechanism
X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=964045f657947f37264da78b5e87f1dc832d384e;p=tomcat7.0

Document Linux performance/overhead of using multi lock mechanism


git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@796362 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/modules/jdbc-pool/doc/jdbc-pool.xml b/modules/jdbc-pool/doc/jdbc-pool.xml
index 0bdef8277..800d89604 100644
--- a/modules/jdbc-pool/doc/jdbc-pool.xml
+++ b/modules/jdbc-pool/doc/jdbc-pool.xml
@@ -354,7 +354,9 @@
       <p>(boolean) Set to true if you wish that calls to getConnection should be treated
          fairly in a true FIFO fashion. This uses the <code>org.apache.tomcat.jdbc.pool.FairBlockingQueue</code> 
          implementation for the list of the idle connections. The default value is <code>false</code>.
-         This flag is required when you want to use asynchronous connection retrieval.
+         This flag is required when you want to use asynchronous connection retrieval.<br/>
+         During performance tests, the fairQueue does very well on a multi core Solaris system,
+         but performs terribly on a Linux Fedora 11 system. On Linux we recommend setting this to false. 
       </p>
     </attribute>