Hello,
i have one more question. :)
I'm using jmeter plugins and there is a "Ultimate Thread Group" which is 
great.So i configure it as follow:1 Thread0 Delay0 Startup60 Sec. Load0 Shutdown
Means launch 1 Thread and send data 60sec long. Perfect.
With this I'm able to sent 209 Emails with SMTP Sampler where one 300bytes file 
is submited. I check the inbox folder with "find . - name f | wc -l" and i also 
check the probe count in my Jmeter report.OK.
Now i increase the Thread to 5 and do the test again.Of cource having 5 Threads 
i can sent more Emails but it's not that many more as i would expect. With 5 
Threads im able to sent "only" 294 Emails. But why do i not get about 1000 
Emails? Doing it with 1 Thread and having 209 i would expect to have something 
like 1000 when doing it with 5 Threads.Now i again increase the Thread to 20 
but the 294 does not change. It's still 294 Emails. ?
Any idea? 
Is it related to my server?

BrGeorge




     Benjamin BALET <[email protected]> schrieb am 16:39 Dienstag, 
14.Juli 2015:
   

 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
> >
> >
> >
>
>
>
>


  

Reply via email to