应用程序性能测试艺术(英文影印版)

.case study 2:call center
summary
4 interpreting results:effectuve root-cause analysis
the analysis process
types of output from a performance test ..
root-cause analysis
analysis checklist
summary
5 application technology and its impact on performance testing
astbcgribiys java and xml(ajax)
citrix
http protocol
java
oracle
sap
service-orientated architecture(soa)
web 2.0
oddball application technologies:help,my load testing tool won't won't record it!
a tranction examples
b poc and performance test quick peference
c automaz tool vendors
d sample kpi monitoring templates
e sample project plan
index ...

.　　Appendix B, POC and Performance Test Quick Reference, reiterates the practical steps presented in the book.
　　Appendix C, Automated Tool Vendors, lists sources for the technologies required by performance testing. It is not an endorsement and is not intended to be complete.
　　Appendix D, Sample KPI Monitoring Templates, provides some examples of the sort of Key Performance Indicators you would use to monitor server and network performance as part of a typical performance test configuration.
　　Appendix E, Sample Project Plan, provides an example of a typical performance test plan based on Microsoft Project.
　　Conventions Used in This Book
　　The following typographical conventions will be used.
　　Italic
　　Indicates new terms, URLs, email addresses, filenames, and file extensions.
　　Constant width
　　Used for program listings and also within paragraphs to refer to program elements such as variable or function names, databases, data types, environment variables, statements, and keywords.
　　Constant width bold
　　Shows commands or other text that should be typed literally by the user.
　　Constant width italic
　　Shows text that should be replaced with user-supplied values or by values determined by context.
　　TIP
　　This icon signifies a tip, suggestion, or general note.
　　CAUTION
　　This icon indicates a warning or caution.
　　Glossary
　　The following terms are used in this book.
　　Application landscape
　　A generic term describing the server and network infrastructure required to deploy a software application.
　　ICA
　　Citrix proprietary protocol, Independent Computing Architecture.
　　ITIL
　　Information Technology Infrastructure Library. ..
　　ITPM
　　Information Technology Portfolio Management.
　　ITSM
　　Information Technology Service Management.
　　JMS
　　Java Message Service (formerly Java Message Queue).
　　Load injector
　　A PC or server used as part of an automated'performance testing solution to simulate real end-user activity.
　　IBM/WebSphere MQ
　　IBM's Message Oriented Middleware.
　　POC
　　Proof of Concept, a term used to describe a pilot project often included as part of the sales cycle. The intention is to compare the proposed software solution to a customer's, current application and so employ a familiar frame of reference. Proof of value is another term for a POC or Proof of Concept.
　　SOA
　　Service-Oriented Architecture
　　Transaction
　　A set of end-user actions that represent typical application activity. A typical transaction might be: log in, navigate to a search dialog, enter a search string, click the search button, and log out. Transactions form the basis of automated performance testing.
　　Using Code Examples
　　This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless you're reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O'Reilly books does require permission. Answering a question by tieing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product's documentation does require permission.
　　We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: 'The Art of Application PerFormance Testing by Ian Molyneaux. Copyright 2009 Ian Molyneaux, 978-0-596-52066-3."
　　If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at permissions@oreilly.com.
　　Safari Enabled
　　When you see a Safari Enabled icon on the cover of your favorite technology book, that means the book is available online through the O'Reilly Network Safari Bookshelf.
　　Safari offers a solution that's better than e-books. It's a virtual library that lets you easily search thousands of top tech books, cut and paste code samples, download chapters, and find quick answers when you need the most accurate, current information. Try it for free at http://safari.oreilly.com.
　　How to Contact Us
　　Please address comments and questions concerning this book to the publisher:
　　O'Reilly Media, Inc.
　　1005 Gravenstein Highway North
　　Sebastopol, CA 95472
　　800-998-9938 (in the United States or Canada)
　　707-829-0515 (international or local)
　　707 829-0104 (fax)
　　We have a web page for this book, where we list errata, examples, and any additional information. You can access this page at:
　　http://www.oreilly.com/catalog/9780596520663
　　To comment or ask technical questions about this book, send email to:
　　bookquestions@oreilly.com
　　For more information about our books, conferences, Resource Centers, and the O'Reilly Network, see our web site at:
　　http://www.oreilly.com
　　Acknowledgments
　　Many thanks to everyone at O'Reilly who helped to make this book possible and put up with the fumbling efforts of a novice author. These'include editor Andy Oram, assistant editor Isabel Kunkle, managing editor Marlowe Shaeffer, Robert Romano for the figures and artwork, Jacquelynn Mcllvaine and Karen Crosby for setting up my blog and providing me with the materials to start writing, and Karen Crosby and Keith Fahlgren for setting up the DocBook repository and answering all my questions.
　　In addition I would like to thank my employer, Compuware Corporation, for their kind permission to use screenshots from a number of their performance solutions to help illustrate points in this book.
　　I would also like to thank the following specialists for their comments and assistance on a previous draft: Peter Cole, President and CTO of Greenhat, for his help with understanding and expanding on the SOA performance testing model; Adam Brown of Quotium; David Collier-Brown of Sun Microsystems; Matt St. Onge; Paul Gerrard, principal of Gerrard consulting; Francois MacDonald of Compuware's Professional Services division; and Alexandre Mechain from Compuware France.
　　Finally, I would like to thank the many software testers and consultants whom I have worked with over the last decade. Without your help, this book would not have been written! ...