Interview Extract - Performance testing

Reference: http://www.whatistesting.com/interviews/sbarber.htm

" Scott Barber is the person behind www.perftestplus.com, co-founder of WOPR (the Workshop On Performance and Reliability) and a prolific writer. In this interview he explains what performance testing is, how one should go about learning it, various resources that can help you and many more things. If you want to ask him more questions or you want to send any feedback on this interview, please send it to webmaster @ whatistesting.com. "

If one wants to gain expertise in performance testing what all should one do? What are the tools, books and sites that can be helpful?
There is very little consolidated information out there about the type of performance testing that most organizations need. There is no doubt that my site (http://www.perfetsplus.com) and articles are one of the most complete references for “Practical Performance Testing”. However, it is by no means complete. Some of the other places I have learned valuable lessons that I have applied to performance testing are:
* Everything I can find written by Alberto Savoia
* Lessons Learned in Software Testing, John Wiley & Sons, 2002 by Cem Kaner, James Bach and Brett Pettichord.
* Testing Computer Software (2nd Ed.), International Thomson Computer Press, 1993 by Cem Kaner, Jack Falk, & Hung Quoc Nguyen.
* Select Chapters from The Web Testing Handbook, STQE Publishers, 2001 by Steve Splaine and Stefan P. Jaskiel.
* Research published by performance tool vendors.
* Research published by testing and research organizations such as Nielsen//NetRatings, Keynote Systems, Inc., and IEEE
* Online forums and magazines such as StickyMinds.com, QAForums.com and stpmag.com and performancetester.com.
* Performance Engineering of Software Systems, Addison-Wesley, 1990 by Connie U. Smith, Ph.D.
* Scaling for E-Business: technologies, models, performance, and capacity planning, Prentice Hall, 2000 by Daniel A. Menascé, Ph.D.
* Speed Up Your Site, New Riders, 2003 by Andrew B. King
* Anything by Cem Kaner, James Bach, Jerry Weinburg and/or Edward Tufte.
These days, I continue learning through networking with experts, being a technical editor for new performance related publications, beta testing tools, hosting and/or attending workshops and conferences and assisting with research being led by other experts and students in the field.To really grow your career as a performance tester, I believe there are several things you can do that will gain you largest benefit.
* Become a “Mid-Level Everything” – Developer, DBA, Network Admin, Systems Admin, Architect, Business Analyst, etc.
* Become an expert in the following – your tools, performance analysis, relevant aspects of operational research and statistics, consolidating, interpreting, sorting, and graphically presenting complex information in an intuitive format.
* Become skilled/knowledgeable in the following areas – group facilitation, product management and training.
* Find a mentor. There are several exceptional performance testers out there who believe in Jerry Weinburg’s consulting principle “Give your best work away for free.” Befriending one (or more) of them to ask questions of, share ideas and brainstorm with is amazingly useful… to everyone involved.

What is your opinion about the state of performance testing tools? Are there some open source or free tools available?
Most tools on the market aren’t actually Performance Testing tools, they are Load Generation tools. No matter what the tool vendors claim, they do not make performance testing simple, they do not analyze results, and they do not pinpoint performance issues. They are virtually all grossly overpriced, and never believe the demo. That said, I have a favorite tool that I support heavily… with a long list of caveats. My favorite is my favorite because it allows me to create realistic loads by writing custom functions and procedures in C – rather than trying to guess how to make the silly GUI buttons duplicate the workload I have constructed. The best OpenSource tool for general web based load generation is OpenSTA. As long as you are only testing websites, it is competitive with the major (pay) tools in terms of actual ability to generate load and collect data. There are plenty of other free niche tools for specific platforms and protocols, but they are only useful to small groups of people doing very specific types of testing.

How do you combine performance testing with load and stress testing
Actually, I see Performance Testing as a superset of testing that includes load and stress testing. I often refer to it as “Performance Related Testing”. In general, load testing is testing your application under expected load conditions to determine the overall performance. Stress testing is testing your application under unexpected or extreme conditions to determine failure modes so you can protect against them. In my presentation “Introduction to Performance Testing; The Who, What, Where, When and Why.” (available here) I describe various components of Performance Testing, and the process in general.

Keep that DBA job in ten ways

Reference: http://www.rampant-books.com/art_freeman_interview.htm

" By Robert Westervelt, SearchOracle.com writer10 Aug 2003 SearchOracle.com

Robert Freeman, author of Oracle9i New Features and Oracle 9i RMAN Backup & Recovery, is currently working on a book about the Oracle 10G database, which will be unveiled at OracleWorld in September. He recently talked with SearchOracle.com about the most common DBA mistakes he sees while working as a technical consultant for Lombard, Ill.-based TUSC, which provides consulting services to Oracle clients. "

Make backup and recovery a top priority. Without good backup and recovery systems, DBAs can be guaranteed two things: IT disasters and unemployment. DBAs need to make data recovery their primary focus.

Lock out unused Oracle accounts. When you create a database, Oracle creates a number of ancillary accounts for a variety of Oracle Enterprise Manager (OEM) functions. Remember to lock out these unused accounts to outside users. If Oracle 9i is installed manually, then the ancillary accounts could remain open and create a hole in the system.

Put the production database in archive log mode. Running the database in archive log mode allows hot backups to be performed while the database is open and available. It also allows recovery of the database in the event of a failure. To avoid loss of critical data, an archive log is absolutely necessary.

Set privileges on data files. Unless the files are encrypted, someone knowledgeable in how Oracle stores data could access the files. Only those who need access to the data should be given privileges. In Unix, Oracle data files will allow anyone read/write access, unless DBAs set specific privileges.

Follow a prescribed set of standards when creating and administrating the database. Often a DBA will create a database without any standards for setting objects and creating a set of schemas. A lack of standards usually lands DBAs in a mess.

Don't use new features before they're ready for prime time. A lot of the newest database features often need time to prove themselves. A good DBA is versed in new features but knows when and when not to use them. Any bugs in the new feature could cause the loss of valuable information.

Always be on the lookout for trouble. It's important to set up a robust proactive monitoring program. For example, DBAs need to watch how much space they have free in the database and, as that number shrinks, they need to go in and make a planned change to increase the space.
Find a mentor. This is very important for new and midlevel DBAs, because the Oracle database encompasses so much technology. Find someone who is experienced and really knows what they are doing. Look for a mentor online, in DBA forums, or find one at work.

Read everything. Educate yourself as best as possible by keeping up with the latest technology and practices. This means knowing relational database technology, online transaction processing and data warehouse technology.

Trust nothing (at the outset). Don't trust everything you read at first glance. No two Oracle installations are the same.