Lightening The Load-Testing Load



Email    print   
January 1, 2007 —  (Page 1 of 3)
John Camp remembers it like it was yesterday.

Just as 34,000 students at Wayne State University were getting ready to begin a new semester, the Web application that lets them sign up for classes froze. “It locked up for a full two hours, and students resorted to registering by phone,” said Camp, CIO for the Detroit-based university. “[Administrators] were concerned that enrollment would fall.”

The culprit turned out to be the database that drove the application. “No one had exposed it to a full load of 1,000 simultaneous registrations,” he said. “We had tested 10,000 functional transactions, but we had not tested a true simulation of everything.”

Camp’s experience is not uncommon. Load testing—making sure an application will perform well under expected usage—is a tricky business. It requires intimate knowledge of everything, from how an application works and how users are likely to interact with it, to how the production environment is set up, according to analysts, development managers and tool makers. “You have to peer into all the tiers. There are so many moving bits and pieces, so many places where problems can occur,” said Mark Eshelby, product manager for Compuware, which sells testing and other application life-cycle tools. “If you don’t [load test thoroughly enough], you are going to have problems when you go live,” added Camp, who learned that lesson the hard way.

Part of the problem for many shops is that load testing remains an afterthought in the development process, even though the impact of poor performance on the business is well understood, said Voke analyst Theresa Lanowitz. Instead of simply running load tests just before applications are deployed, development teams should architect apps from the get-go with “what-if” performance scenarios in mind, she said. They should also allocate enough time to fix the flaws they find, she added. “You should [set aside] four weeks in June to test the Christmas Web site.”

A planned approach lets testers find out a number of things: “What happens when a Web shopper places an item in a shopping cart? What happens when you decrease the bandwidth? What happens when you have 10,000 [such transactions] coming down the line?” said Eshelby.




Pages 1 2 3 


Share this link: http://sdt.bz/29966
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Mu Dynamics Launches Cloud-Based Load Testing Solution for Mobile Applications and APIs
Blitz Accelerates Developers' Deployment Time, Offers Affordable and Continuous Testing Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb