Browsers and third party applications connecting to the system under test have processing time too...
What you should monitor is the computer running your JMeter script and/or the slave machines hosting the JMeter scripts. If they exceed 80% (or whatever arbitrary value) of CPU time or if you notice an excessive bandwith on these computers you must add Jmeter slaves to your load testing infrastructure. 2015-07-14 16:28 GMT+02:00 George <[email protected]>: > Hi, > well yea for sure JMeter need "time" to create the socket the connection > and sent the data - clearly.I do also accept the "think times" of > JMeter.What i mean is if we can say that JMeter is basically sending the > request out as fast as it is possible for JMeter - right?So there is no > "speed up" value.If i want to stress my server i just need to multiple the > load by putting more threads or seting up more jmeter instances and > multiple the load with every instance.This is also clear for me. > > Of course i noticed that if i set the "connection timeout" values to e.g. > 1ms than the requests goes out very fast but they are all red (fail) > because telling jmeter to close the connection after 1ms is very stupid :) > BrGeorge > > > > Adrian Speteanu <[email protected]> schrieb am 16:14 Dienstag, > 14.Juli 2015: > > > Hi, > > I had a test script of a very small server requests (pinging the webapp > basically). JMeter recorded 5ms average response times, monitoring on the > server side showed 2ms average response times. The difference is > justifiable due to the load-balancer in between the test client machine and > the targeted server + jmeter's own "think times". Anything at the level of > the millisecond is easily considerable acceptable. What do you mean by > speeding up? > > Cheers, > Adrian > > On Tue, Jul 14, 2015 at 3:55 PM, George <[email protected]> wrote: > > > Hello, > > i have a question about JMeter's performance. > > > > I have a simple test plan with one thread looping 1000 times > > I have one SMTP sampler targeting my smtp server on port 25 and sending a > > file of couple Kb.I have no connection timeout or connection close > defined. > > Technically everything works perfect. > > I know i could put some "timer" or "sleep" to slow down sending my smtp > > request e.g. i put a "sleep 10" and jmeter waits 10 sec between every > smtp > > sampler, but what about to "speed up" the sending process?I mean how > "fast" > > do JMeter sent out the smtp request? Is it related to my environement? > > Can i "speed up" jmeter somehow? > > I have the same question for http as well. > > BrGeorge > > > > > > > > > >
