Web tools

Thanks Ken,
I wanted to see what kind of load this server would handle
and I have only one PC to try it from so I am not exactly
sure how to load test this server.

 >Do you want 1,000 concurrent *requests*? or 1,000
concurrent *users*?

what is the difference?

Do you want to test a single webpage? or an entire web
application?

Entire web application.

This will be an e-commerce web and complete with shopping
cart and credit card processing. So I need to know before
I put it into production and look like an ass.

Thanks Ken and by the way you and Jonathan have great
sites!
Joe


 >-----Original Message-----
 >Hi,
 >
 >Do you want 1,000 concurrent *requests*? or 1,000
concurrent *users*?
 >Do you want to test a single webpage? or an entire web
application?
 >
 >To setup the requisite number of requests so you can set
the number of
 >threads and socket multiplier on the client(s). For that
many concurrent
 >requests you should probably be using multiple client
machines. Also, make
 >sure that you have enough network bandwidth! If you only
have, say, 1.5
 >MB/sec, then this will probably be saturated by 30
concurrent requests from
 >dial-up users!
 >
 >Now, to simulate "users", you need to decide how often
these users make
 >requests. Usually a real-life user would get a page, then
spend some time
 >reading the page. So, 1,000 concurrent users might only
be 50 concurrent
 >requests.
 >
 >Cheers
 >Ken
 >
 >
 >
 >"Joe" <anonymous DeleteThis @discussions.microsoft.com> wrote in
message
 >news:111ca01c44139$b5c5b1b0$a501280a@phx.gbl...
 >: Hello
 >:
 >: I tried the webtool group no luck just advertisments.
 >:
 >: I wanted to know how to use this tool Webstress Tool
from
 >: MS .
 >:
 >: How can I, or how do I set up a thousnad concurrent
users
 >: to test my web please. Maybe a help site would be great
 >: too!
 >:
 >: thanks
 >: Joe
 >:
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Web tools 

What do you mean "what is the difference"? I explained the difference.

A request is a physical request - the HTTP request is coming into the
server, and the server is sending it back
A "user" is someone using your site. A typical user issues a request, then
reads the response (eg reads a webpage, or fills in a form), then issues a
new request sometime later.

So, 10,000 concurrent users might only mean 500 concurrent requests, because
not all users are actively seeking new pages from the webserver.

If you read the WAST online help, you will see plenty of information on how
to configure WAST to issue a set of requests one after the other. You can
either record a session, or you can manually enter the requisite URLs, and
any additional HTTP information (such as POST, or GET data, cookies etc)

Cheers
Ken

"Joe" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
news:118c401c441b6$cae0f410$a501280a@phx.gbl...
: Thanks Ken,
: I wanted to see what kind of load this server would handle
: and I have only one PC to try it from so I am not exactly
: sure how to load test this server.
:
: >Do you want 1,000 concurrent *requests*? or 1,000
: concurrent *users*?
:
: what is the difference?
:
: Do you want to test a single webpage? or an entire web
: application?
:
: Entire web application.
:
: This will be an e-commerce web and complete with shopping
: cart and credit card processing. So I need to know before
: I put it into production and look like an ass.
:
: Thanks Ken and by the way you and Jonathan have great
: sites!
: Joe
:
:
: >-----Original Message-----
: >Hi,
: >
: >Do you want 1,000 concurrent *requests*? or 1,000
: concurrent *users*?
: >Do you want to test a single webpage? or an entire web
: application?
: >
: >To setup the requisite number of requests so you can set
: the number of
: >threads and socket multiplier on the client(s). For that
: many concurrent
: >requests you should probably be using multiple client
: machines. Also, make
: >sure that you have enough network bandwidth! If you only
: have, say, 1.5
: >MB/sec, then this will probably be saturated by 30
: concurrent requests from
: >dial-up users!
: >
: >Now, to simulate "users", you need to decide how often
: these users make
: >requests. Usually a real-life user would get a page, then
: spend some time
: >reading the page. So, 1,000 concurrent users might only
: be 50 concurrent
: >requests.
: >
: >Cheers
: >Ken
: >
: >
: >
: >"Joe" <anonymous.RemoveThis@discussions.microsoft.com> wrote in
: message
: >news:111ca01c44139$b5c5b1b0$a501280a@phx.gbl...
: >: Hello
: >:
: >: I tried the webtool group no luck just advertisments.
: >:
: >: I wanted to know how to use this tool Webstress Tool
: from
: >: MS .
: >:
: >: How can I, or how do I set up a thousnad concurrent
: users
: >: to test my web please. Maybe a help site would be great
: >: too!
: >:
: >: thanks
: >: Joe
: >:
: >
: >
: >.
: >
 >> Stay informed about: Web tools 

Thank you Ken Sorry for the late reply
Joe
 >-----Original Message-----
 >What do you mean "what is the difference"? I explained
the difference.
 >
 >A request is a physical request - the HTTP request is
coming into the
 >server, and the server is sending it back
 >A "user" is someone using your site. A typical user
issues a request, then
 >reads the response (eg reads a webpage, or fills in a
form), then issues a
 >new request sometime later.
 >
 >So, 10,000 concurrent users might only mean 500
concurrent requests, because
 >not all users are actively seeking new pages from the
webserver.
 >
 >If you read the WAST online help, you will see plenty of
information on how
 >to configure WAST to issue a set of requests one after
the other. You can
 >either record a session, or you can manually enter the
requisite URLs, and
 >any additional HTTP information (such as POST, or GET
data, cookies etc)
 >
 >Cheers
 >Ken
 >
 >"Joe" <anonymous.TakeThisOut@discussions.microsoft.com> wrote in
message
 >news:118c401c441b6$cae0f410$a501280a@phx.gbl...
 >: Thanks Ken,
 >: I wanted to see what kind of load this server would
handle
 >: and I have only one PC to try it from so I am not
exactly
 >: sure how to load test this server.
 >:
 >: >Do you want 1,000 concurrent *requests*? or 1,000
 >: concurrent *users*?
 >:
 >: what is the difference?
 >:
 >: Do you want to test a single webpage? or an entire web
 >: application?
 >:
 >: Entire web application.
 >:
 >: This will be an e-commerce web and complete with
shopping
 >: cart and credit card processing. So I need to know
before
 >: I put it into production and look like an ass.
 >:
 >: Thanks Ken and by the way you and Jonathan have great
 >: sites!
 >: Joe
 >:
 >:
 >: >-----Original Message-----
 >: >Hi,
 >: >
 >: >Do you want 1,000 concurrent *requests*? or 1,000
 >: concurrent *users*?
 >: >Do you want to test a single webpage? or an entire web
 >: application?
 >: >
 >: >To setup the requisite number of requests so you can
set
 >: the number of
 >: >threads and socket multiplier on the client(s). For
that
 >: many concurrent
 >: >requests you should probably be using multiple client
 >: machines. Also, make
 >: >sure that you have enough network bandwidth! If you
only
 >: have, say, 1.5
 >: >MB/sec, then this will probably be saturated by 30
 >: concurrent requests from
 >: >dial-up users!
 >: >
 >: >Now, to simulate "users", you need to decide how often
 >: these users make
 >: >requests. Usually a real-life user would get a page,
then
 >: spend some time
 >: >reading the page. So, 1,000 concurrent users might only
 >: be 50 concurrent
 >: >requests.
 >: >
 >: >Cheers
 >: >Ken
 >: >
 >: >
 >: >
 >: >"Joe" <anonymous.TakeThisOut@discussions.microsoft.com> wrote in
 >: message
 >: >news:111ca01c44139$b5c5b1b0$a501280a@phx.gbl...
 >: >: Hello
 >: >:
 >: >: I tried the webtool group no luck just advertisments.
 >: >:
 >: >: I wanted to know how to use this tool Webstress Tool
 >: from
 >: >: MS .
 >: >:
 >: >: How can I, or how do I set up a thousnad concurrent
 >: users
 >: >: to test my web please. Maybe a help site would be
great
 >: >: too!
 >: >:
 >: >: thanks
 >: >: Joe
 >: >:
 >: >
 >: >
 >: >.
 >: >
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Web tools