NULL博文链接：https://lee2013.iteye.com/blog/2092137Starting the TestAt this point, you are ready to start load testing If you want to double check the slave systems areworking open jmeter log in notepad you should see the following in the logJmeter engine. RemoteJMeterEnginelmpl: Starting backing engineIf you do not see this message, it means jmeter-server did not start correctly. For tips on debuggingthe issue, go to the tips section There are two ways to initiate the test: a single system and allsystemsStart a single clientssimpleText jmxFile Edit Search Run Options Help回amHb。es1 planRemote startlocalhostThread Grd Remate Start AllCtrlShift-R192.168.0.12Http r StopCtrI-PeriodName: Test PlarG Aggreg ShutdownCtrl commaCurrenlyWorkBenchRemote stopRemote stop AllAlt-XRemote shutdownRemote shutdown all Alt-2Remote exlRemote exit allClearCtrl Shifi-EClear AllCtrl-E1. click Run at the top2. select remote start3. select the ip addressStart all clientssimplest.myFile Edit SearchRunOntionsHelpStartCtrl-RStan no pausesTestRemote startThreac Grd Remote Start AllTest PlanHttp F Stoptrl-PeriodName: Test PlanAggreg shutdowntrI Comma‖ commentWorkBench Remote StopRemote stop AllAlt-XRemote shutdownRemote shutdown All Alt-ZRemote exitRemote exit allClearctrl+shift-EClear AllCtrl-E1. click Run at the top2. select remote start all or use crtl-z3/4LimitationsThere are some basic limitations for distributed testing Here's the list of the known items in nospecific order.1. RMI cannot communicate across subnets without a proxy; therefore neither can jmeter without aproxy2. Since jMeter sends all the test results to the controlling console, it is easy to saturate thenetwork IO. It is a good idea to use the simple data writer to save the results and view the filelater with one of the graph listeners3. Unless the server is a large multi processor system, in most cases 1-2 clients is sufficient tooverwhelm the server4. A single JMeter client running on a 2-3 Ghz CPU (recent cpu)can handle 300-600 threadsdepending on the type of test. (The exception is the webservices). XML processing is CPUintensive and will rapidly consume all the cpu cycles. as a general rule, the performance of XMLcentric applications will perform 4-10 slower than applications using binary protocolsAdditional resourceshttp://wiki.apache.org/imeter/jmeterfaq#howtodoremotetestingthe.27properway.27.3fhttp://imeter.apache.org/usermanual/remote-test.htmPsIn some cases, the Firewall may still be blocking RMi trafficSymantec Anti Virus and FirewallIn some cases, Symantec firewall needs to be stopped from windows servicesopen control panel2. open administrative tools3. double click services4. Go to down to symantec anti virus, right click and select stopWindows firewallopen network connections2. select the network connection3. right click and select properties4. select advanced tab5. uncheck internet connection firewallLinUXOn Suse linux, ipchains is turned on by default For instructions please refer to the"remote testingin the user manualOn redHat(or derivatives), iptables (netfilter)is turned on by default. Execute"service iptablesstop"to stop the linux netfilter firewall