On 14/07/2009, Deepak Shetty <[email protected]> wrote: > hi > possible problems that i can think of are > a. You have loaded the Jmeter client with more load than it can handle (as a > rule of thumb i wouldn't run more than 20-25 threads from a single client
That very much depends on the test plan (and the host, of course). It should be possible to run many more threads for many test plans, say 200-300. One way to check if JMeter is the limiting factor is to compare the result of running a single instance of JMeter against two instances, each with half the number of threads. > jmeter). You would need to distribute your test across multiple machines > (You can check whether your machine is overloaded by using your OS specific > perf monitoring tool - reliability and perf monitor on windows) > b. There is something that you need to tweak in your tests(e.g. if your > application uses caches , and the browser based tests are hitting the cache, > whereas the Jmeter tests are not) > c. You are downloading embedded resources (e.g. big flash/movie files or > something whereas the browser either has it cached or is streaming it).This > can easily be tested by checking your script and clearing your browser cache > before accessing the site while your load test is running. > > regards > > deepak > > > On Tue, Jul 14, 2009 at 3:03 AM, ziohausam <[email protected]> wrote: > > > > > Hello All, > > > > I have a Question. > > > > I use Jmeter in my Performance test execution. > > > > Actually i always face drawback when number of users increases and of > > course > > this is normal. > > > > what is not normal is that while i check the performance live with the test > > execution running, i open a browser session for navigating the web > > application and i can't find any drawbacks. also i try this from different > > PCs, and no noticeable drawbacks. > > > > For example: > > in the testing tool, some request takes 2 seconds with 1 user. and 90 > > seconds with 75 users running with ramp-up period 40 seconds. that's fine > > that's a noticeable drawback. but actually when i use the same PC or any > > different PC to call this request though the browser while it is processed > > by the test tool, i find no noticeable drawbacks. > > > > How can i explain this? how can i understand this, and also how can i > > distinguish performance drawback source (server, application, client > > machine > > hardware or bandwidth, etc) > > > > I had sent this post before in QA forums and had really helpful ideas to > > explain the reason, but they still do not represent the real cause as i > > have > > checked all suggestions and found every thing is ok. i hope i can find more > > ideas and explanations here too > > am > > Note: as i am only a beginner using JMETER. most possibly is that i am > > missing something configuring my tool or test execution process. > > > > > > Regards, > > Hosam > > -- > > View this message in context: > > > http://www.nabble.com/How-to-distinguish-performance-drawback-source-tp24476707p24476707.html > > Sent from the JMeter - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
