On 17/10/2008, rustix <[EMAIL PROTECTED]> wrote: > > i've created a wap application using java and wml. this system has to be able > to support 24000 concurrent sessions at a given time. how could i carry this > out? i'm hoping to use JMeter
24000 concurrent sessions is a large number - too big for a single JMeter instance - or indeed a single host, unless connections are shared. However, how many of them actually need to be active at any one time? And what constitutes a session? Is there a login process to establish the session? There may be ways to set up JMeter to send requests that look to the application that they are coming from different sessions, but which in fact are coming from the same JMeter thread - e.g. by interleaving requests with different session ids (not sure how easy that will be; depends on the session tracking). A simple test plan on a fast host can probably handle 500-1000 threads; beyond that one needs to use multiple instances. But note that the request load generated by a single JMeter thread can far exceed that generated by a human user. http://wiki.apache.org/jakarta-jmeter/HowManyThreads > -- > View this message in context: > http://www.nabble.com/-Help--Checking-number-of-concurrent-session-with-JMeter--tp20032128p20032128.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]
