You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/12/17 15:20:32 UTC
DO NOT REPLY [Bug 25591] New: -
AnchorModifier test runs rather slowly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25591>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25591
AnchorModifier test runs rather slowly
Summary: AnchorModifier test runs rather slowly
Product: JMeter
Version: unspecified
Platform: All
URL: http://http://
OS/Version: Other
Status: NEW
Severity: Minor
Priority: Other
Component: HTTP
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: sebb@apache.org
It looks as though the AnchorModifier parser runs rather slowly:
For example:
junit
-Dtest.case=org.apache.jmeter.junit.protocol.http.parser.HtmlParserTester
-Dtest.format=plain
[...]
[junit] Testcase: testSimpleParse took 0.831 sec
[junit] Testcase: testSimpleParse2 took 0.02 sec
[junit] Testcase: testSimpleParse3 took 0.04 sec
[junit] Testcase: testSimpleParse4 took 0.01 sec
[junit] Testcase: testSimpleParse5 took 0.01 sec
[junit] Testcase: testFailSimpleParse1 took 0.01 sec
[junit] Testcase: testFailSimpleParse3 took 0.01 sec
[junit] Testcase: testFailSimpleParse2 took 0.07 sec
[junit] Testcase: testSimpleFormParse took 5.018 sec
[junit] Testcase: testBadCharParse took 5.037 sec
I tried another test of testSimpleFormParse without the call to parser.process
(), and it was much quicker.
Not sure how much AnchorModifier is used, but might be worth investigating this.
Also, why is the first test longer?
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org