Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of t.p.ellison@gmail.com
 designates 72.14.220.154 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding;
        b=VU/L/4Q4gND8g9El9hEPQE+Zvq7rBJSzdKpuLNqeOziy3lb0ZMSIuukzyu8jXrFzkMQEq4G70GBDFx5G0nQL3kAzNKXpwZPQL/28FW7jurjktOWnVKrVeIoT0MhaWjoFqGiRaZnFwwiCFjSVDJWJ273tTJElICAlmPVmbzA/gVs=
Message-ID: <47F49F28.8050003@gmail.com>
Date: Thu, 03 Apr 2008 10:11:04 +0100
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: [classlib][pack200] Sped up hashCode and removed dead getCpAll()
  (HARMONY-5682)
References: <2083037913.1207161568650.JavaMail.jira@brutus>
In-Reply-To: <2083037913.1207161568650.JavaMail.jira@brutus>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Andrew Cornwall (JIRA) wrote:
> I didn't do that because I assumed the overhead of the exception
> handler would be too much. But it's worth a try - so I just did. Here
> are the results for my testcase:
> 
> CpClass 0.685 3.066 Without exception handler: 0.685 s With exception
> handler: 3.066 s
> 
> CpRef Without exception handler: 1.204 s With exception handler:
> 1.873 s
> 
> CPUTF8 Without exception handler: 2.323 s With exception handler:
> 6.761 s
> 
> In other words, with exception handlers our time for hashCode almost
> doubles. Since hashCode accounts for slightly more than 10% of the
> total time of the test case with the exception handlers and less than
> 4% without, I'm inclined to leave the exceptions uncaught.

Interesting.  Are you running those tests with the IBM VM or the DRLVM?

I'm assuming that the difference in performance is due to the JITs 
reluctance to in-line the longer version of hashCode() since the 
exception handler itself should make no difference.

Regards,
Tim