STB Suite

Bus Analyzer Module (BAM) in action

Introduction

Here are some example screenshots of BAM capturing an I/O session to a native SATA attached SSD drive. Also is an example STB Suite DMM (Disk Manufacturing Module) log file of the session which generated the I/O.

As a point of reference, all of the test functionality of DMM and BAM are also available via api calls using the STB Suite Developer Toolbox (DTB) API.

A BAM trace captured via the DTB API calls may be read into the BAM GUI to obtain the post-capture analysis.

BAM – Trace Data showing queuing

This is a sample of the trace data showing the captured phases as they happened in time.

The series of Data-In phases are the results of WRITE commands issued above in the time-line.

BAM Post-Capture Analysis – 1

This is the Trace Performance Analysis report BAM generates.

Showing various performance metrics, etc

A trace which was captured via DTB API calls can be loaded into BAM to get this analysis on any captured data set.

BAM Post Analysis – 2

This report shows the cumulative commands which were captured, etc. along with performance metrics.

 

DMM .Log File

The I/O traffic in this illustration was generated via the STB Suite Disk Manufacturing Module (DMM).

All DMM functionality is also available via the STB Suite Developers Toolbox (DTB) API.

All test parameters shown in the report are configurable, other features such as data compare, complex test types, and low-level functions are available in either DMM or the DMM-functions in the DTB API.

================================================================================
>> SCSI Toolbox32, Version 9. 0. 2 (build) 131007, running on \\W7TEST        <<
>> Default Driver: 10, Operating System: Windows 7<<
>> Number of Drives Under Test: 1 <<
>> Available Memory (in GB): 4.53 <<
================================================================================

Test Date:  07/17/2014  16:55:23
Test Pass:  1

   Device:  4:1024:0   Vendor: KINGSTON, Product: SV300S37A120G   Serial: 50026B773C035485    , Version: 521A

   Capacity: 120.03 GB, BlockSize: 512 (0x200)

Script Filename:  C:\Users\mikej\Documents\1-a-QdTest.seq

Results:

— OPERATOR NAME: mdj

— SPECIAL TEXT: BAM – QD=32
07/17/2014  16:55:23  TEST 1 of 2:
Write Test; Sequential; for 1,000,000 Blocks
Fixed-Length Transfers of 256 (0x0100) Blocks
Start Block: 0
Data Pattern: Decrementing
Queue Depth = 16
FUA = ON
Stop-on-Error Type: Stop Current Test

  07/17/2014  16:55:24  Test Completed Successfully

Transfer Rate: 488.28 MB/sec
I/O Per Second: 3907.00 IO/sec
Number of Blocks Transferred: 1,000,000
Fastest Command Completion Time: 3.603 ms
Slowest Command Completion Time: 21.973 ms
Average Command Completion Time: 4.149 ms
Standard Deviation of Command Completion Times: 1.234 ms

  07/17/2014  16:55:24                                                 PASSED
——————————————————————————
07/17/2014  16:55:24  TEST 2 of 2:
Read Test; Sequential; for 1,000,000 Blocks
Fixed-Length Transfers of 256 (0x0100) Blocks
Start Block: 0
Data Pattern: Decrementing
Queue Depth = 32
FUA = ON
Stop-on-Error Type: Stop Current Test

  07/17/2014  16:55:25  Test Completed Successfully

Transfer Rate: 488.28 MB/sec
I/O Per Second: 3907.00 IO/sec
Number of Blocks Transferred: 1,000,000
Fastest Command Completion Time: 0.923 ms
Slowest Command Completion Time: 11.973 ms
Average Command Completion Time: 8.451 ms
Standard Deviation of Command Completion Times: 0.826 ms

  07/17/2014  16:55:26                                                 PASSED
——————————————————————————