DO NOT REPLY [Bug 26337] New: - Remote Testing - Tuning CPU usage at controller

[bu...@apache.org]

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=26337>.
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=26337

Remote Testing - Tuning CPU usage at controller

           Summary: Remote Testing - Tuning CPU usage at controller
           Product: JMeter
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: performance@applabs.net


When we conduct a remote test with heavier loads always the controller is a 
bottleneck as it utilizes almost all times 100% CPU utilization. 

So as to bridge this gap, we modified two classes (ResultCollector.java and 
RemoteListenerWrapper.java) besides adding 3 properties in 
the 'jmeter.properties' file

These changes provide 3 modes of results transfer from the remote server to the 
controller. Out of these three, 'batch' mode should be used for tuning CPU 
usage at the controller

The attached 'Remote Testing - Tuning CPU usage at controller.zip' contains the 
modified files. It also contains the readme.doc.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org