Tuesday, June 3, 2008

Performance Engineering Tips - A solid plan leads to better results

Creating a performance plan has many challenges, creating a realistic load test has to be one the greatest. Load and performance testing is many times seen as a nice to have. However, no one ever says "yeah, I'm OK if my applications ran slower". As load and data capacity increases, this is exactly what happens. Mid-stream in the operation of business the applications can suddenly start to slow down. This happens usually without warning and almost always has a detrimental impact to the business.

How can you keep this from happening? A better test plan is the place to start.
  1. Review the types of activities that the users will be performing. We call these transactions.
  2. Review the location and amount of users. Take into consideration network speeds.
  3. Review the amount transactions that will be performed.

Many IT performance testers simply look at user count and business transactions. Failing to understand the network conditions the volume of transactions will produce an inadequate simulation.

The better the simulation - the more valuable the predicted operation of the system when it goes live.

1 comment:

Jackie Champion said...

Hey there! Keep it up! This is a good read. I will be looking forward to visit your page again and for your other posts as well. Thank you for sharing your thoughts about performance engineering. I am glad to stop by your site and know more about performance engineering.
One of the objectives of a peformance engineering is to eliminate late system deployment due to performance issues.
Software Performance Engineering is a critical component of Enterprise Risk Management. In today’s complex and interdependent system environments, technology must provide an outstanding user experience for ten’s of thousands users. The new workloads supported by these systems has become increasingly volatile with tremendous variance in average and peak. Peak workloads are no longer simply 3 or 4 times the average. They can rapidly increase to 10 or 20 times the average. Many systems in place today were not designed to rapidly scale to 20X the average. The performance and quality of software or a system is not just a technical issue, but also reflects how well the business operates and performs on a daily basis. In essence, proactive performance engineering is enterprise risk management. PE ensures systems are able to scale with unexpected spikes in system demand whether driven by marketing events, or today's more volatile financial market behavior.