The server logs will monitor access. You may need a log analyser to
assist, such as Webalyser (spelling?).
--
Ron Symonds (Microsoft MVP - FrontPage)
Reply only to group - emails will be deleted unread.
<anon> wrote in message I'm guessing peak time will be first, Fri-Sat 7-10 PM. Then, spread
evenly during the rest of the week. The 40kb would include all files.
(I think this is the normal time an average site is viewed.) These
sites will be only average. Nothing more even though I would like them
to be something special.
Do you know of some software that would allow me to monitor all this?
What is a "peak time"? An hour each day, like rush hour? or two or
three days each month? or each week? Are all 20000 visitors going to
arrive at once like a plague of locusts?
Seriously, using my previous scenario coupled with the up to 30 pages
for each visitor, your server will have to cope with at least 15 pages
per minute, perhaps 45. If a "peak time" is one day each month, then
that 15 ppm becomes 330-990ppm, or 5-16 pages per second (bandwidth
required 200KB - 650KB). Your server will be working hard, but
*might* just cope. But this assumes the visitors are evenly spread
over a ten hour day...
Also assumed is the 40KB page includes images and linked CSS and .js
files.
Spiders turn up at all times of day and night, some go through every
page, some make several visits and spider a few pages at a time. They
all return at irregular intervals.
--
Ron Symonds (Microsoft MVP - FrontPage)
Reply only to group - emails will be deleted unread.
<anon> wrote in message All visitors would probably be in the same time zone. They would
visit at peak times during consecutive 30 day periods. The 20000
would include repeat visitors and each one may look at from 1-30
pages. The sites will consist of roughly 350 pages with the avarge
page size being 40kb.
You mentioned spiders which I haven't even thought about. Please give
me an alternative if you have one.
That is a very difficult question to answer.
Are all the visitors in the same time zone, or equally spread around
the world?
Do they visit on weekends?
Do they sleep?
Does 20000 include repeat visits or are they unique?
Is 20000 pages served, or actual visitors? If visitors, how many
pages?
(Almost) Worst case (All visitors Mon-Fri evenly spread between
8am-6pm, no repeats, 20000 pages served, no pages refreshed)
20000pages/22days/10hours/60minutes=1.5 pages per minute. Your
server will handle this without problems. But is this the right
scenario? And don't forget search engine spiders.
--
Ron Symonds (Microsoft MVP - FrontPage)
Reply only to group - emails will be deleted unread.
<anon> wrote in message
How much bandwidth is needed for roughly 20,000 visitors a month
with an averagr page size of 60kb?
In theory yes.
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
.......................with a computer
<anon> wrote in message
It is 384k bytes per second. Sorry if I confused anyone. This is
another new
area for me. Is my math correct that 6.4, 60kb pages could be
downloaded
simutaneously per second then?
Is that 384K bits or Bytes? If it's 384K bits then, as Jens
remarked, you
are not delivering as fast as I can download (512K
bits/second). You
could serve 6 dialup customers, but anyone on broadband will
find your
server slow.
If its 384K Bytes per second (almost equivalent to 4Mb upload
speed), then
you are on your way. Upload and download speeds are normally
expressed in
bits per second.
--
Ron Symonds (Microsoft MVP - FrontPage)
Reply only to group - emails will be deleted unread.
<anon> wrote in message
Thanks for your answer Ron. I said in error download when I
meant upload.
It is my upload speed that is 384kb. Not lets see if I can
divide
correctly. At 60kb per page (average) visitors could download
6.4 pages
per second simultaneously. Is that correct? If so, maybe that
is enough
to start and I could get more if necessary.
I do not know any formulae, but consider:
I download pages at 60KB/s[1] If your server cannot upload
as fast as I
download, it is slow and will hold me up. Now multiply that
by the
forecast number of simultaneous visitors to the sites and you
have some
idea of the bandwidth requirements. In practice, some
visitors will be
using broadband, some dialup, so there is some averaging to
do here.
IMO 384kb is only suitable for a few simultaneous dialup
customers - and
remember you are uploading, not downloading.
[1] 60KB/s (60K bytes per second) is roughly 512Kb/s (512K
bits per
second) with overheads.
--
Ron Symonds (Microsoft MVP - FrontPage)
Reply only to group - emails will be deleted unread.
<anon> wrote in message
I am in the early stage of hosting my own sites on a Win 2003
server. I
know the general things in preparation for this but know
nothing about
allocating enough bandwidth to insure that visitors are not
slowed down
by my set up. I have checked everything as best I can but
don't know
very much about the various providers and offerings they may
have
currently. I want to start with enough bandwidth which seems
to be about
384kb down. Does anyone know a formula for determining the
correct
amount based on the number of hits or visitors?
