Re: content static for 24hrs
- From: "Sean O'Connor" <zxc1@xxxxxxxxxxx>
- Date: Tue, 31 Jul 2007 12:42:00 +0100
Thank you,
20k visitors, 250k hits per day.
Largely content delivery, some of which will be subscription based. So some
kind of session info would be required.
There are about new 200 pages per day, but the majority of these would be
unpopular, most users only visit a page or two. The new site should be more
sticky, with usage perhaps multiplying by 2-5.
The servers are in house. The are single purpose servers.
sqlserver, w2000,sp4,pentium3,1gb ram, 2 hard drives(one for backups, 1 for
everything else)
web server, w2003,sp1,pentium3,1gb ram, 3 hard drives.
Yes I plan to parameterise using querystrings.
SOC.
"Anthony Jones" <Ant@xxxxxxxxxxxxxxxx> wrote in message
news:eRV0gp10HHA.5408@xxxxxxxxxxxxxxxxxxxxxxx
"Sean O'Connor" <zxc1@xxxxxxxxxxx> wrote in message
news:%23KOGHd10HHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
Would application variables storing the html be advisable?
Just knowing there will be 20-40 thousand requests per day (you meant
requests right?) is it enough info.
Is this simply content delivery or is there some application element where
a
client needs a session?
How many and how large are the pages would you want to cache?
Is this a hosted site or do you own the server(s)?
In what way are they not ideal? (e.g if they have limited memory or many
other applications on them then loading up memory based application
variables may not be what you want to do).
Do you expected to parameterise the content sent by means of querystring
values?
--
Anthony Jones - MVP ASP/ASP.NET
"Sean O'Connor" <zxc1@xxxxxxxxxxx> wrote in messageper
news:eV7VVtr0HHA.5380@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I have been creating sql server driven web sites for a few years.
I now have to create one which will have over 20-40 thousand sessions
day, on servers that are not ideal.
The main content changes once a day.
I've read contradictory advice for improving the performance. e.g wrt
mixing html and asp/application variables.
My normal way of coding is to
-open connections and recordsets late and close early
-using stored procedures
-response.buffer=true
-option explicit
The servers will have connection pooling by default.
The same recordsets will be returned thousands of times a day.
Can anyone advise on further good practice.
Thank Soc.
.
- Follow-Ups:
- Re: content static for 24hrs
- From: Anthony Jones
- Re: content static for 24hrs
- References:
- content static for 24hrs
- From: Sean O'Connor
- Re: content static for 24hrs
- From: Sean O'Connor
- Re: content static for 24hrs
- From: Anthony Jones
- content static for 24hrs
- Prev by Date: Re: content static for 24hrs
- Next by Date: Re: content static for 24hrs
- Previous by thread: Re: content static for 24hrs
- Next by thread: Re: content static for 24hrs
- Index(es):
Relevant Pages
|