[ http://issues.apache.org/jira/browse/BEEHIVE-106?page=history ] jamie zyskowski closed BEEHIVE-106: -----------------------------------
closing > Controls Perf Regression: 3X increase in scenario times > ------------------------------------------------------- > > Key: BEEHIVE-106 > URL: http://issues.apache.org/jira/browse/BEEHIVE-106 > Project: Beehive > Type: Bug > Components: Controls > Versions: V1Beta > Environment: 2 x 2.8GHz | win2k | hotspot 1.5.0-b64 > Reporter: jamie zyskowski > Assignee: jamie zyskowski > > description: > The regression seems to have been introduced somewhere between rev76140 and > rev109265. It occurs standalone and in a jpf/tomcat env. There are two > scenarios that show the regression. The first uses a custom control that has > one method which takes a string and returns the length of the string > [StrlenPgmTest]. The second takes a variable number of integer args and > returns the sum of their values [VarargsPgmTest]. Interestingly, a third > scenario that takes an integer and returns a string of the int size does NOT > show this regression [VarretPgmTest]. > steps to repro (standalone for simplicity): > cd $BEEHVIE_HOME/controls/test/perf > ant rebuild > cd bin > . ./perf.sh StrlenPgmTest > expected result (within 20% of this time value): > TEST: org.apache.beehive.controls.perf.standalone.StrlenPgmTest > hash=-1989672960 > time=4026 > actual result: > TEST: org.apache.beehive.controls.perf.standalone.StrlenPgmTest > hash=-1989672960 > time=13938 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
