Last post Feb 26, 2015 04:12 AM by vineeta_2010
Feb 14, 2015 11:06 PM|vineeta_2010|LINK
I have to handle a web application where more than 900000 people will hit my website .
what kind of additional features I have to add so that
my website doesn't get slow.Please help me.I am using asp.net C# ,Ms sql server 2008
Feb 15, 2015 12:39 AM|ignatandrei|LINK
You must explain better your requirements and your site
If it is just a plain html site and the customer can to see 1 page with a hour delay then you just do nothing.
If it is a database driven site and 1 millisecond is not acceptable as a delay, you have a great deal to work.
Feb 15, 2015 01:30 AM|vineeta_2010|LINK
thank you for your suggestion yes it is database(MS SQL SERVER) driven site,that's why I am worried .It is actually a web application where nearly 10,0000 job applicant will search
there information and download there admit card online.
Feb 15, 2015 04:43 AM|PatriceSc|LINK
Create indexes where it makes sense. I assume that each user will fetch only a much smaller subset? Create that volume of rows to load test your app and see what happens. You also have management views to watch out performance.
I's a bit hard to start from something you just suspect rather to work starting from some actual issue.
Feb 15, 2015 09:48 AM|smirnov|LINK
more than 900000 records
more than 900000 people will hit my website
900.000 records is not the same as 900.000 people and it sounds very unlikely
Anyway, you need to follow some best practices and
- make sure that database connection is always properly closed
- cache data whenever it makes sense (i.e. if you display "we have 10,0000 jobs" - do not request that number out of the database)
- when you do search and it potentially returns hundreds of records - do not return all of them just piece by piece (page by page)
Feb 15, 2015 03:38 PM|vineeta_2010|LINK
Feb 16, 2015 04:08 AM|smirnov|LINK
While typically asp.net and sql server will handle that amount of data without any problem, it all depends on multiple factors such as
- server environment (which is probably out of topic here),
- database design
- html design
- asp.net design
For asp.net I told you few things above.
For database - most critical parts are:
- listing of many data (e.g. browsing products by category)
If such functionality exists then make sure you use indexes on tables, do not return all records in one short (page by page), cache or precalculate data (e.g. if you have listing with number of products in each category then do not count that number on each
call - count it once when you add product and save somewhere).
For html design - some best practices are: try to make less external files (e.g. instead of having multiple css files - put all styles in one css). Minify css. Optimize images. Multiple images that used everywhere on site (e.g. logo, navigation, etc) could
be combine in one (css sprite). This reduces the round trips required to display your page, making your site faster, which might be not really related to asp-programming but still usefull to do.
Feb 21, 2015 07:25 AM|vineeta_2010|LINK
thanks a lot I really appreciate you . can you please suggest some thing about server environment from where I can get information about server environment
Feb 21, 2015 11:42 AM|smirnov|LINK
It's hard to say anything without any information about your application and its current setup. What I meant is there are multiple factors and even you'd have a good designed application it could work unstable due to insufficient server environment. Again,
it's hard to say what could be "wrong", e.g.
- if web server and database server on the on the same physical machine, it might be not have enough resources for both (e.g. RAM, CPU, etc). Both IIS and Sql attempt to reserve memory for future operations and they are better being on seperate servers to
stop unnecessary memory allocation/deallocation and paging operations.
- server is shared (used by multiple web sites or multiple databases)
- server software (IIS, Sql) is outdated. E.g. Sql 2008 is about 7 years old now. It is still good one, but if you care about performance (scale, etc) - think about having a recent version.
- physical server does not correspond to software requirements
- and so on
Feb 26, 2015 04:12 AM|vineeta_2010|LINK
thank you so much...