Running a Asp.net website with MS SQL server - When should i worry about scalability? -
I run a medium-sized website on an ASP.net platform and use MS SQL Server to store data I do
My current site statistics are: <6 p> ~ 6000 page one day ~ 10 tables provide approximately ~ 10 tables per page service per page with approximately 1000 rows • 1GB RAM in the hosting machine
I expect to hit around near the end of 2009:
~ 20,000 page views ~ 10 tables and approximately 4000 lines per table ~ 5 questions per page
My question is, can I still plan for scalability? The candidate will catch the machine by the end of the year with statistics.
I know that my description is very high level and does not provide insight into the types of inquiries. But just want to know what your intuition says?
You should always plan for scalability.
Will the machine be caught by the end of the year
The path is too small to answer the information if this is a page request through four questions per page. Due to large-scale contact with heritage enterprise applications, it takes 30 CPU seconds to process - so there is no way. If it is taking the minimum fraction of the second to serve some stable content stored in the cache, and your query is only executed every half hour to refresh the content - then you are correct by the rate of traffic increase by 2020 Are there.
My guess is that you are somewhere close to the latter scenario. 20,000 pages are not actually a ton of traffic in a day, but you have to benchmark your page and server performance at some point so that you can calculate your requirement.
Two years ago I had a relatively new (two years ago) laptop To run IIS and 1100 to 1200 simple dynamic page request per second was founded by a consulting firm whose business is suited for ASP.net websites. Was doing, but it shows you how much you can.
Comments
Post a Comment