Errata

The Art of Application Performance Testing

Errata for The Art of Application Performance Testing

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Printed
Page 1
3 paragraph

you repeat the word "despite" twice in line 4.

Note from the Author or Editor:
Please delete one instance of "twice"

 Gilberto Munoz  Jul 29, 2010  Sep 20, 2013
PDF
Page 12
Bold font "Note" part


In following sentence:
"these scale from simple capture and organization to solutions with
full-blown Universal Modeling Language (UML) compliance."

Universal Modeling Language (UML)
should be modifed to
Unified Modeling Language (UML)




Note from the Author or Editor:
Please change to "Unified Modeling Language (UML)"

 Zhonghua Li  Dec 08, 2010  Sep 20, 2013
Printed
Page 18
Under "sizing of application databases"

Text:

"The size of the test environment database"

Should be:

"The size and content of the test environment database"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
Printed
Page 20
Last line of "Physical versus virtual NIC"

Text:

"I always advise minimizing"

Should be:

"I always advise maximizing"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
Printed
Page 33
Paragraph under - Identify all input data requirements and expected responses

This is the information that needs to entered by the user
should be:
This is the information that needs to be entered by the user

 Anonymous  Mar 26, 2013  Sep 20, 2013
Printed
Page 40
After "Pacing" heading

Reads "Think Time And Think time" - assume this should read "Think Time And Pacing"

Note from the Author or Editor:
This should read as indicated

"Think time and Pacing"

 Barry Perez  Jun 17, 2010  Sep 20, 2013
Printed
Page 40
5th paragraph under heading 'Pacing'

You have written: <q>...if a typical "mini-statement" transaction takes 60 seconds to execute, then applying a pacing value of 2 minutes will limit the maximum number of transactions of this type per hour to 30 per virtual user. This is accomplished by making each virtual user wait 2 minutes before beginning the next iteration. In other words, the amount of time between each execution of "mini-statement" cannot be less than 2 minutes.</q>

This might appear to be pedantic of me: if the transaction takes 60 seconds to execute and the user must wait 2 minutes before beginnning the next iteration, then one such transaction will be completed only every 3 minutes, giving 20 transactions of this type per hour.
Of course, it will all depend on the Pacing support from the tool: the Pacing delay might begin once a transaction has completed, or each iteration may be separated by a fixed time interval.

Note from the Author or Editor:
Quite correct!

Please change "30 per hour" to "20 per hour"

 Andrew Parker  Nov 14, 2012  Sep 20, 2013
Printed
Page 40
Paragraph heading Pacing

Paragraph Heading: "Pacing"

Should be:

Paragraph heading: "Think Time and Pacing"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
Printed
Page 40
First line of paragraph: Pacing

Text: "Think Time and Think Time"

Should read:

"Think Time"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
Printed
Page 41
Last paragraph, 2nd line

"You should prorate"

Should read:

"You should configure"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
Printed
Page 48
Mainframe Tier Paragraph

The last sentence of the paragraph reads,

Note from the Author or Editor:
Hi,

Many thanks for spotting this, the line should read as follows:

"The most common are:"

 Steve Eckhart  Aug 10, 2009  Sep 20, 2013
Printed
Page 52
Second line under "Proof of Concept Checklist"

"but you can anticipate"

should read:

"but you should anticipate"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
Printed
Page 53
point 5

Access to an person who is familiar with the application
should be:
Access to a person who is familiar with the application

 Anonymous  Mar 26, 2013  Sep 20, 2013
Printed
Page 54
First line of first bullet point under "Deliverables"

"of the technical suitability of your"

should read:

"of the technical suitability of the"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
Printed
Page 60
2nd line, 2nd bullet point

"(except the"

Should read:

"(except possibly the"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
PDF
Page 62
First bullet point

You have written <q>It is all too easy to be caught without insufficient injector capacity...</q>

The word <q>insufficient</q> should be replaced with the word <q>sufficient</q>.

Note from the Author or Editor:
Many thanks for picking this up.

Please change insufficient to sufficient

 Andrew Parker  Dec 06, 2012  Sep 20, 2013
Printed
Page 70
3rd line under "Transaction Scripting"

"rare to require"

Should read:

"to require"

Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
Printed
Page 78
Paragraph in middle of page

what you should you expect to see ...
should be:
what should you expect to see ...

 Anonymous  Mar 26, 2013  Sep 20, 2013
Printed
Page 91
Last line of second paragraph under "Scalability and Response Time"

"of the performance and"

Should read:

"of the performance test and"

 Ian Molyneaux
Ian Molyneaux
 		 Sep 10, 2013  Sep 20, 2013
PDF
Page 135
Figure D-2

Figure D-2. Example server KPIs for Microsoft IIS. The figure displayed is the same figure as Figure D-3 for Citrix server farm and does not appear to be the KPI for MS IIS.

Note from the Author or Editor:
Figure D-3 incorrectly used for Figure D-2. Please amend Figure D-2 to use the correct image file.

 Russell Barnes  Jul 12, 2011  Sep 20, 2013
PDF
Page 137
second paragraph

the URL link as described in appendix E cannot be found

The MS Project file is available from the book?s companion web site (http://oreilly.com/
catalog/9780596520663/).

Note from the Author or Editor:
Can you please confirm where I can upload the sample project file so that it will be available to readers?

 Kostas Hairopoulos  Apr 05, 2010  Sep 20, 2013