Project viability question - 3000 users over 3 weeks

antic

antic

Perch
I need a quickish answer to this one if possible...

I have a client wanting to run an ASP/MSSQL web application I wrote for them, for 3000 of their staff (gov't department) over about 3 weeks. This involves emails (plain text) going out to all of them each week, plus approx. 50 hits to the web app per person.

So that's 3000 text emails sent (all at once) every 7 days, and 150,000 hits to the app over the 3 weeks.

How viable is it to run this on a shared server? The app is fairly straightforward, but will the server handle the load?

Cheers!
 
Should be ok, we have higher hit sites than that, how many possible on at one time may be the question, as RAM usage could get extreme esp if using sessions.
 
Thanks for the quick response Stephen!

It's just a short online survey, probably 1 ASP page which saves the data (15 questions) in MSSQL. I'm keeping the front end very simple, survey HTML will be static. No session data (will probably turn session state off in code if that helps).

Realistically, 10 hits per person (welcome page, survey, submit & thankyou, and a few images). Not sure how many simultaneously at peak, but assume 100. If no sessions being used (if I can turn em off in code) then hopefully that's all ok?

[EDIT] Main question might be emails. Is that number ok with you - 3000 out at once, each week over 4 weeks? Probably most to the same domain. All small, simple HTML, no embeds or attachments.

Cheers!
 
As long as no spam complaints it should be fine :D Batches of 500 at a time or less would be preferrable, but as long as it is not a continually running list of 3000 it should be tolerable.
 
You must log in or register to reply here.
Back
Top