Re: increasing the RPS of any page
- From: "John Rivers" <first10@xxxxxxxxxxxxxx>
- Date: 30 Aug 2005 01:15:13 -0700
I think a good approach is to:
- always bear in mind that your pages may get called 100 times per
second
- create a quick and easy to use testing app (that can simulate high
traffic)
- performance test as you develop, getting ridding of slow or cpu
hungry code as you work
- study database locking and indexing till you are a pro
- create and use consistent database access strategy (generally
tablock/tablockx for all web stuff can
accelerate db access significantly as lock acquisition time for web
apps is often higher than lock hold time)
- never use connected recordsets for long winded update jobs
- make sure connection pooling is on!
- try and avoid approaches that don't work with data in small chunks
(ie: DataReader yes, DataSet avoid like plague)
- asp.net trace timing feature is cool, use this to drill down into
inefficient methods
- remember that http requests are serialized for each session context
(issue if using frames)
- remember that response.write(your html) is probably much more
efficient than using ms html and web controls (which suck)
also bear in mind the big difference between slow through waiting (low
cpu) and slow through processing (high cpu)
.
- References:
- increasing the RPS of any page
- From: ashok
- Re: increasing the RPS of any page
- From: tom pester
- increasing the RPS of any page
- Prev by Date: Re: Folder for database
- Next by Date: general question
- Previous by thread: Re: increasing the RPS of any page
- Next by thread: ASP.Net transfer across domains
- Index(es):
Relevant Pages
|