Experts, Can anyone comment on this?
On Wed, Feb 26, 2014 at 1:16 PM, Perf Test <[email protected]> wrote: > Dear Deepak Shetty, > > I'm so glad to see your detailed clarification, I think you are right, > However if i'm going to do a concurrent users load test, according to your > case i will have to chose option b) . then shouldn't we require to use > think time with option b)? > > When i use think time with option 'b)' i couldn't load all 100 users > threads concurrently (but all the 100 logins successful) , but when i > remove the think time i.e. reduce the rampup time i was able to load 100 > concurrent users. do you think it is right way of testing concurrent users > load? > > Thanks, > Sam > > > > > On Tue, Feb 25, 2014 at 10:40 PM, Deepak Shetty <[email protected]> wrote: > >> No it depends on your definition of "active" - the common definitions I >> have heard of is >> a) active - has a session on your system but not necessarily doing >> anything >> - may be reading the article or typing in a form but not clicking submit ( >> b) concurrent - actually doing something like clicked a link or submitted >> a >> form >> (though I have also heard it being used interchangeably) >> For these definitions >> a) only has meaning for memory usage and if you dont use the session much >> , >> its not really relevant except when you want to closely model real world >> behavior (think times etc) and check cache performances and expiry or if >> you do use session then it is important >> >> b) is usually the more relevant attribute for performance tests. >> >> >> >> On Tue, Feb 25, 2014 at 4:08 AM, Deepak Goel <[email protected]> wrote: >> >> > It is probably the same >> > On 25 Feb 2014 11:42, "Perf Test" <[email protected]> wrote: >> > >> > > Dear All, >> > > >> > > What is the Difference between JM 'concurrent users' load of 100 and >> > > 'Active users' 100 testing for a given time period. >> > > >> > > >> > > Thanks. >> > > Sam >> > > >> > >> > >
