When testing your databases for performance, you have a couple of options: testing transactions per second (TPS) or response time. But which test gives you a better indication of the health of your database?
In this Quest white paper, Domain Expert Kevin Dalton defines both TPS and response time, and makes the case for why the more popular test (TPS) may not always be the right metric for database performance.
About the Author:Kevin Dalton is the Manager of Software Development for Quest’s Benchmark Factory for Databases. One of the original architects of the product, Kevin has been working on its development for more than 10 years. He has experience with several database technologies, including Oracle, SQL Server, Sybase, MySQL, and IBM UDB. Kevin holds a bachelor’s degree in electrical engineering and has been involved in software development since 1989.
Acquisitions - Enstratius, RemoteScan, StatSoft