my old presentation to teach people how to use the benchmark tool developed by my team.

1. HP
Performance
Tracking
Part 2 - Client

2. Why use a custom Client?
• The custom client allows HP to include custom color coded HP limits.
– The custom HP limits allow HP to control when a SI should be written.
– SIs drive the process to correct issues.
• The custom HP client zips up the results which provides a consistent way for ODMs to report results. Not
just a jpeg screen capture like the Microsoft Assessment Kit (ADK).
• The custom client allows HP to capture additional information automatically from the system. E.g.
Software build ID, motherboard.
• The custom client allows HP to add additional tests. E.g. First Logon Command Time.
• It is important to understand that HP Perftrack uses the same tests as the ADK and therefore gets the same
results.

3. Test
Selection
• The standard HP Perftrack is much smaller than
the ADK. Approximately 70Mbytes instead of
2Gbytes.
• HP Perftrack achieves this by leaving out the
media test files from the standard distribution.
• When you install the standard HP Perftrack the
media tests will not be available.
• You can add the media tests by unzipping the
media files to the same directory as you run the
HP Perftrack installation. The HP Perftrack
installer will then pick them up and all the tests
will be available.
• HP Perftrack customizes the default list of tests
and limits based on HP product line. Detected
using the type 1 SMBIOS.

4. Test Selection
• There is a difference between tests
available and those that are selected by
default.
• Here all the tests are available but only the
defaults are selected.
• E.g. Photo handling requires the media
files and would not show up at all with the
default install. With the media files
installed it becomes a valid selection but is
not selected by default.
• The default selection is the same
regardless of whether the media files are
available

5. HP Perftrack Results
• Results can be found in the C:ADKResults
directory
• Datasubmission results are used to upload to the
sharepoint and attach to SIs since they are
smaller.
• Archive results are huge but contain the full
information required to debug the issue.
• Key information files are found in the System
Profile directory.
• Report.html (main results)
• DetailReport.html (detailed results for each run)
• IssueReport.html (issues reported by Microsoft)

6. Interworking with the Windows Assessment Console (WAC)
• HP Perftrack results are fully compatible and may be viewed with the WAC if desired.
• Most of the time you do not need to use the WAC.
• Note that if you use the datasubmission zip you will not be able to view the detailed etl files because they
are not contained in the datasubmission zip. They are only contained in the archive zip.
• Step 1- Install the assessement tools from the Microsoft ADK. This does not have to be on the target
system.
• Step2 – Unzip the datasubmission or archive zip file.
• Step 3 Run the WAC and open the xml results file. You now have full access to the results in the WAC.

7. Note this does not have to be on the target machine.
Select the following options to install the
WAC

8. Interworking with the Windows Assessment Console (WAC)
• 1. Unzip the datasubmission or archive zip file.

9. Interworking with the Windows Assessment Console (WAC)
• Use Open Results to open the
Job Results xml File
• After clicking on Open Results
use the Browse button on the
next screen to navigate to the
Job Results XML file and open it.

10. The Windows Assessment Console
Note that for the etl links at the right to work you must use the archive zip file because
the etl files are required. The datasubmission file does not contain the large etl files.

11. The Windows Performance Analyzer
When you click on one of the etl files displayed
On the RHS of the WAC you actually launch the
WPA (Windows Performance Analyzer).
You can also launch the WPA directly to view
Any etl file.

12. What is new in the Windows 8.1 version of HP Perftrack?
• Two new measurements from Microsoft (neither checked by default)
• Internet Explorer Security Software Impact
• Windows Store Apps Performance
• Report.htm (standard results page) now lists multiple hard drives and multiple graphics
• BIOS Post limits are now set dependent on the size of the boot hard drive (see WHQL)
• SSD detection reliability improved and new SSD field added on report page
• Some elementary processing of boot trace files done but WAC more comprehensive
New Microsoft Measurements

13. Example 1: Find the cause of the Fast Boot Shutdown issue
Using what you have learned find the reason for the Fast Boot Shutdown Time exceeding
the HP Perftrack limit of 10 seconds.
Hint: For this case use the WPA to view the Job Results xml file captured by HP Perftrack.
1.) What is the average Fast Boot Shutdown Time?
2.) What is principal cause of the issue?
3.) How would you prove your answer to 2.
The datasubmission zip file can be found at
bugkiller.americas.hpqcorp.netPublic_ShareWorkingEricTDC_Perftrack_trainingshutdown

14. Example 2: Find the cause of the slow FLC time
FLC = First Logon Commands
There is a limit on 1st boot that HP may not run any commands that take longer than 30 seconds.
In this case the commands took around 69.9 seconds. Determine what caused the issue.
Hints: For this case use the Windows Performance Analyzer to Analyze the etl trace. The HP
commands are run by an executable called RUNCMDS.EXE. Try to find out why RUNCMDS.EXE is
taking so long.
The etl trace file can be found at
bugkiller.americas.hpqcorp.netpublic_shareworkingericTDC_Perftrack_trainingFirstLogonCommands

15. Backup

16. Thank you