Performance Testing practice

Last month, my project has been conducted a performance testing.
I will share some tips.

some paramters
1. Online user: 400
2. Think time: 3s(strict, base on the scenario)

Below is my conclusion. please post your advice and comments.

 

Practice

l         Finding the issue is more important than how to resolve them

l         Resolve the concurrent issue in the TC phase, such the 2 related dropdown list data retrieved

[Advice] Include the Load Test (VS2005 Team Suite) to the UT package

l         Importance of the baseline, include the

u       Source Code(branch)

u       Database(back up, import and export only schema, not the entire database)

1)      DB Backup command

2)      Sqlplus system/password@ltfms

3)      Create directory fms_loaddata as ‘g:"’;

4)      Drop user training cascade

5)      Export data command:Expdp system/password@ltfms content=data_only directory=fms_loaddata schemas=training dumpfile=ltfms20070815.dmp

6)      Import data command:Impdp system/password@ltfms content=data_only directory=fms_loaddata schemas=training dumpfile=ltfms20070815.dmp

l         In the design phase, should consider some case, such as the SQL function usage (upper) etc.

l         Use the correct select cope, select * should be considered before u use it.

Best Practice

l         Web cache is very important, such as the procedure info, common dropdownlist value, etc

l         Load Balance

u       By request: Config the same session state server and machine key in the web.config file

u       By IP: Config the same session state server in the web.config file

l         IIS performance Tuning

During the PT, the pressure focuses in the web side first, so we should optimize the IIS in the best status

1) If you use the by request load balance, please undo the below image check box(red area)

        

2) Adjust the web garden in your IIS application pool, default is 1(Advice: 3 is for the single CPU pc, 6 is for the dual CPU pc in SZ)
 

l         Debug step by step

1)      Debug Viewer

http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx

using code:  System.Diagnostics.Trace.WriteLine();// Not web trace!

d2.Subtract(d1)).Milliseconds

You can use this tool to select the worst code section via the above diagnostics.

l         Oracle EM

Using this to view

1)      Top SQL
 

2)      Adjust the SGA

 
Tips

1)      Setup a new DB for PT, please optimize the db table space and index

2)      After some rounds PT, please adjust each table space capacity and SGA if need

3)      Before a new round PT, conducting a warm up test is a very useful for ASP.NET web application

4)      Set up  <compilationdebug="true"> to  <compilationdebug="false"> when u deploy the web app to IIS

5)      When u record scripts via web test, if exceptions, please use the command to try to resolve it: iisreset

6)      If possible, please conduct a round test on the framework