Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of ohad.shacham@gmail.com
 designates 209.85.217.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=K8st3u7mbj8Ih4wmnepynvYAAndC6taU7qDF8dA7g5V2vfuE8+rQ5y/l29k/vaIlLu
         jSVkwDL8rog0a4FPmZp3PObgvUHqhr9BahL/J+ELiKX5XaQM5Yt9fvJwKC0f1foJBcXU
         Y4XlOVMj4gOrGf0dt5b8A4YQnuuQ4CFveDm+w=
MIME-Version: 1.0
Date: Sun, 8 Nov 2009 16:47:25 +0200
Message-ID: <11d0e1fc0911080647k7769f620w72f0c2c59fdee80f@mail.gmail.com>
Subject: ConcurrentHashMap
From: Ohad Shacham <ohad.shacham@gmail.com>
To: dev@tomcat.apache.org
Content-Type: multipart/alternative; boundary=0016e647626acbef7a0477dd27e7

--0016e647626acbef7a0477dd27e7
Content-Type: text/plain; charset=ISO-8859-1

Hi,


I noticed that in version 6.0.20 several Hashtables and HashMaps were
replaced by ConcurrentHashMaps. I have noticed that many Hashtables were not
replaced; therefore, I assume that a contention detection tool was used to
identify the contended Hashtables. I would be happy to know if this is the
case and also whether a scalability and/or performance improvement was
achieved by switching these collections with concurrent ones.


Thanks,

Ohad

--0016e647626acbef7a0477dd27e7--