We're updating the issue view to help you get more done. 

jbb2005 performance regression

Description

jbb2005 seems to have taken two discrete hits over the past couple of months which leave us at 82% of our most recent best.

The following graph tells the story:

http://jikesrvm.anu.edu.au/cattrack/results/rvmx86lnx32.anu.edu.au/commit.1012/production/Performance/SPECjbb2005/SPECjbb2005/SPECjbb2005.large.png

The first big hit was apparently due to the nano timer commit (r13209), which apparently jbb2005 did not properly recover from.

The second hit is a little less obvious (between r14403 and r14425).

Unless anyone has better ideas immediately, I'm prepared to take an exhaustive look at the revisions between 14403 and 14425 to try to get a clearer picture.

Environment

x86lnx

Status

Assignee

DaveG

Reporter

Steve Blackburn

Labels

None

External issue ID

None

Fix versions

Affects versions

2.9.2

Priority

Medium