SNolan wrote:I learned from our webmaster that our site has around 65,000 unique visitors per month.
How can that help me in planning my load tests?
Thanks a bunch.
65,000 unique visitors is interesting to know; that's about
91 unique visitors per hour on average. Call it 100/hour.
But if 90 of those 100 only visit one page and don't do anything
very deep, that's not that big a deal.
But the real numbers you want are:
* number of simultaneous users at one time, min/average/max.
* length of time of visit, min/average/max
* total data volume of the sessions min/average/max
* what is the longest, most-difficult scenario or use
case you expect.
The design of the overall load-test scenario has to take
all of this into account. Certainly the "analytics" from
the web servers can help here.
(Also, it may make a difference to know how many errors the
database system reports...it may be useful/realistic to
toss in one or two tests that intentionally cause an error.)
Hope this answers you question.
eValid LoadTest Spport