You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Nguyen Dao <mr...@gmail.com> on 2009/05/11 20:46:20 UTC
ThreadGroup and User Login Account
Hi everyone,
I need to load test a JSF application with 500 users, and need your
tips/recommendations on how to go about doing that. Please help!
*MY CURRENT TEST PLAN:*
**
ThreadGroup1 (100 threads)
-- Login
-- Search for a record of type # 1
-- Switching between different views
-- Logout
ThreadGroup2 (100 threads)
-- Login
-- Search for a record of type # 2
-- Switching between different views
-- Logout
ThreadGroup3 (100 threads)
-- Login
-- Search for a record of type # 1
-- Switching between different views
-- Logout
ThreadGroup4 (100 threads)
-- Login
-- Search for a record of type # 1
-- Switching between different views
-- Logout
ThreadGroup5 (100 threads)
-- Login
-- Search for a record of type # 1
-- Switching between different views
-- Logout
*QUESTIONS:*
**
(1) How to configure each thread to use a unique test login account? The
application does not allow one login account to have two concurrent
logged-on sessions. For example, if thread # 1 of ThreadGroup1 logs on
using testuser1, then thread # 2 of ThreadGroup1 must use something else,
otherwise the session for thread # will be expired/destroyed requiring a
logging in again.
(2) What is a popular practice for load testing many users? Creating 500
test login accounts sounds a bit overkill.
Thank you,
Nguyen Dao
mr.nguyendao@gmail.com
Re: ThreadGroup and User Login Account
Posted by Nguyen Dao <mr...@gmail.com>.
Thank you. User Parameters Pre Processor works for getting each thread a
unique user login.
On Mon, May 11, 2009 at 3:10 PM, Deepak Shetty <sh...@gmail.com> wrote:
> 1. You can use a User Parameters Pre Processor to use a different username
> and password for each thread group. You can use a module controller so that
> you define the Login test in one place and just change the data you pass to
> it
> 2. Depends on your requirement. If you wish to test unique users then that
> is what you have to do , (since using the same username may give you better
> results if your application does caching. In test environments we simply
> update the password to known values and query the database to give us N
> number of usernames and use those, dunno how popular this approach is :)
> We also sometimes combine the creation of the user process as part of the
> script.
> regards
> deepak
>
>
> On Mon, May 11, 2009 at 11:46 AM, Nguyen Dao <mr...@gmail.com>
> wrote:
>
> > Hi everyone,
> >
> > I need to load test a JSF application with 500 users, and need your
> > tips/recommendations on how to go about doing that. Please help!
> >
> > *MY CURRENT TEST PLAN:*
> > **
> > ThreadGroup1 (100 threads)
> > -- Login
> > -- Search for a record of type # 1
> > -- Switching between different views
> > -- Logout
> >
> > ThreadGroup2 (100 threads)
> > -- Login
> > -- Search for a record of type # 2
> > -- Switching between different views
> > -- Logout
> >
> > ThreadGroup3 (100 threads)
> > -- Login
> > -- Search for a record of type # 1
> > -- Switching between different views
> > -- Logout
> >
> > ThreadGroup4 (100 threads)
> > -- Login
> > -- Search for a record of type # 1
> > -- Switching between different views
> > -- Logout
> >
> > ThreadGroup5 (100 threads)
> > -- Login
> > -- Search for a record of type # 1
> > -- Switching between different views
> > -- Logout
> >
> > *QUESTIONS:*
> > **
> > (1) How to configure each thread to use a unique test login account? The
> > application does not allow one login account to have two concurrent
> > logged-on sessions. For example, if thread # 1 of ThreadGroup1 logs on
> > using testuser1, then thread # 2 of ThreadGroup1 must use something else,
> > otherwise the session for thread # will be expired/destroyed requiring a
> > logging in again.
> >
> > (2) What is a popular practice for load testing many users? Creating 500
> > test login accounts sounds a bit overkill.
> >
> >
> >
> > Thank you,
> > Nguyen Dao
> > mr.nguyendao@gmail.com
> >
>
Re: ThreadGroup and User Login Account
Posted by Deepak Shetty <sh...@gmail.com>.
1. You can use a User Parameters Pre Processor to use a different username
and password for each thread group. You can use a module controller so that
you define the Login test in one place and just change the data you pass to
it
2. Depends on your requirement. If you wish to test unique users then that
is what you have to do , (since using the same username may give you better
results if your application does caching. In test environments we simply
update the password to known values and query the database to give us N
number of usernames and use those, dunno how popular this approach is :)
We also sometimes combine the creation of the user process as part of the
script.
regards
deepak
On Mon, May 11, 2009 at 11:46 AM, Nguyen Dao <mr...@gmail.com> wrote:
> Hi everyone,
>
> I need to load test a JSF application with 500 users, and need your
> tips/recommendations on how to go about doing that. Please help!
>
> *MY CURRENT TEST PLAN:*
> **
> ThreadGroup1 (100 threads)
> -- Login
> -- Search for a record of type # 1
> -- Switching between different views
> -- Logout
>
> ThreadGroup2 (100 threads)
> -- Login
> -- Search for a record of type # 2
> -- Switching between different views
> -- Logout
>
> ThreadGroup3 (100 threads)
> -- Login
> -- Search for a record of type # 1
> -- Switching between different views
> -- Logout
>
> ThreadGroup4 (100 threads)
> -- Login
> -- Search for a record of type # 1
> -- Switching between different views
> -- Logout
>
> ThreadGroup5 (100 threads)
> -- Login
> -- Search for a record of type # 1
> -- Switching between different views
> -- Logout
>
> *QUESTIONS:*
> **
> (1) How to configure each thread to use a unique test login account? The
> application does not allow one login account to have two concurrent
> logged-on sessions. For example, if thread # 1 of ThreadGroup1 logs on
> using testuser1, then thread # 2 of ThreadGroup1 must use something else,
> otherwise the session for thread # will be expired/destroyed requiring a
> logging in again.
>
> (2) What is a popular practice for load testing many users? Creating 500
> test login accounts sounds a bit overkill.
>
>
>
> Thank you,
> Nguyen Dao
> mr.nguyendao@gmail.com
>