Page tree
Skip to end of metadata
Go to start of metadata

This topic contains the following sections:

Overview

The Benchmark Alignment scheduler task validates, parses, and loads data from XML files.

Use XML files that adhere to following DTD schema when adding or updating benchmarks (see Uploading benchmark data):

<!DOCTYPE [>
  <!ELEMENT BENCHMARK_DATA (BENCHMARK)>
  <!ELEMENT BENCHMARK (BENCHMARK_DEF?,BENCHMARK_RESULTS)>
  <!ELEMENT BENCHMARK_DEF (LABEL+)>
  <!ATTLIST BENCHMARK_DEF BENCHMARK CDATA #REQUIRED>
  <!ATTLIST BENCHMARK_DEF NAME CDATA #IMPLIED>
  <!ATTLIST BENCHMARK_DEF CDATA DESCRIPTION #IMPLIED>
  <!ATTLIST BENCHMARK_DEF CDATA APPLIESTO #IMPLIED>
  <!ATTLIST BENCHMARK_DEF URL CDATA #IMPLIED>
  <!ATTLIST BENCHMARK_DEF DELETE CDATA #IMPLIED>
  <!ELEMENT LABEL>
  <!ATTLIST LABEL NAME CDATA #REQUIRED>
  <!ATTLIST LABEL TYPE CDATA #REQUIRED>
  <!ATTLIST LABEL MANDATORY CDATA #IMPLIED>
  <!ELEMENT BENCHMARK_RESULTS (BENCHMARK_ENTRY+)>
  <!ATTLIST BENCHMARK_RESULTS BENCHMARK CDATA #REQUIRED>
  <!ATTLIST BENCHMARK_RESULTS DELETE CDATA #IMPLIED>
  <!ELEMENT BENCHMARK_ENTRY (BENCHMARK_ENTRY_PROPS+)>
  <!ELEMENT BENCHMARK_ENTRY_PROPS NAME CDATA #REQUIRED>
  <!ELEMENT BENCHMARK_ENTRY_PROPS VALUE CDATA #REQUIRED>
]>

A benchmark file consists of two main sections:

Benchmark definition

Note

The benchmark definition section of the XML file contains definitions of new benchmarks. You do not need to include a benchmark definition section when updating an existing benchmark.

The following table lists the attributes of the BENCHMARK_DEF node.

Element node

Attribute name

Description

Mandatory

Default value

BENCHMARK_DEF

BENCHMARK

Unique benchmark identifier 1

Y

 

BENCHMARK_DEF

NAME

Benchmark name

N

null

BENCHMARK_DEF

DESCRIPTION

Benchmark description

N

null

BENCHMARK_DEF

APPLIESTO

Benchmark application (CPU or STORAGE)

Y

 

BENCHMARK_DEF

URL

Benchmark reference URL

N

null

BENCHMARK_DEF

DELETE

Delete benchmark definition (true or false) 2

N

false


1 Identifiers CFP2000, CFP2000rate, CFP2006, CFP2006rate, CINT2000, CINT2000rate, CINT2006, CINT2006rate, SPC-1, SPC-2, SPC-2_LDB, SPC-2_LFP, SPC-2_VOD, TPC-C are reserved and are not available as identifiers for new benchmarks.
2 Setting this parameter to true will cause the elimination of all related benchmark results. In order to delete a benchmark definition, you must specify its mandatory properties (BENCHMARK and APPLIESTO).

The benchmark definition includes a list of fields (key properties, non-key properties, and results) used to describe the benchmark itself.

Element node

Attribute name

Description

Mandatory

Default value

LABEL

NAME

Field name

Y

 

LABEL

TYPE

Field type (KEY or PROP or RESULT)

Y

 

LABEL

MANDATORY

Specified if field must be considered as mandatory

N

false


Fields marked as MANDATORY are used to validate benchmark input, while properties set as KEY are used to distinguish unique benchmarks.

Note

Benchmarks with the same key are considered identical and only the latest result is maintained in the database, overwriting previous results.

Only field names listed in the following table are available for benchmark definition, as they are linked to models and analyses available in BMC TrueSight Capacity Optimization (speed-up calculation or consolidation for what-if analyses and queuing network models).

Field name Description Internal field type
Mandatory
CPU
Storage
Speedup Consolidation 3 Speedup Consolidation 3
baseline Baseline result double N N N N
cachel1 First level cache string N N N N
cachel2 Second level cache string N N N N
cacheother Other cache string N N N N
chips Number of chips int N N N N
company Company description string Y Y Y Y
compiler Compiler description string N N N N
cores Number of cores int Y Y N N
coresperchip Number of cores per chip int N N N N
cpu CPU description of benchmarked system string N N N N
cpusorderable Number of CPUs that can be ordered string N N N N
hwavail Hardware availability (dd/mm/yyy) date N N N N
memory Memory description string N N N N
opsys Operating system string N N N N
other Other notes string N N N N
processormhz Processor frequency int N Y N N
published Pubblication date (dd/mm/yyy) date N N N N
result Result double Y Y Y Y
storconf Storage configuration string N N N N
storcontroller Storage controller string N N N N
stordisks Storage disk description string N N N N
storports Storage ports description string N N N N
storstreamused Storage stream used int N N N N
stortech Storage technology description string N N N N
swavail Software availability of benchmarked system (dd/mm/yyy) date N N N N
system Benchmarked system description string Y Y Y Y
testdate Test date (dd/mm/yyy) date N N N N
testedby Name of person responsible for the test string N N N N
updated Update date (dd/mm/yyy) date N N N N

3 For consolidation purposes, results must be expressed as rates (bytes per second).

Benchmark results

You can upload results to a benchmark using BENCHMARK_ENTRY_PROPS elements, which enable you to set properties and results for the specified benchmark.

Element node

Attribute name

Description

Mandatory

Default value

BENCHMARK_RESULTS

BENCHMARK

Unique benchmark identifier

Y

 

BENCHMARK_RESULTS

DELETE

Delete benchmark results (true or false) 4

N

false

BENCHMARK_ENTRY_PROPS

NAME

Field name

Y

 

BENCHMARK_ENTRY_PROPS

VALUE

Field value

Y

 


4 To delete a benchmark result, you must specify its key properties.

Note

All fields marked as KEY or MANDATORY in the benchmark definition must be described in the results reporting section. The XML code is validated against these fields before inserting or updating benchmarks.

Available benchmarks

The following table lists the benchmarks that are delivered in BMC TrueSight Capacity Optimization and the fields supported by each group of benchmarks, and shows whether a field is mandatory.

Benchmark Description Field name Field type Mandatory
CFP2000
CFP2000rate
CFP2006
CFP2006rate
CINT2000
CINT2000rate
CINT2006
CINT2006rate
Standard Performance Evaluation Corporation benchmarks baseline RESULT N
cachel1 PROP N
cachel2 PROP N
cacheother PROP N
chips PROP N
company KEY Y
compiler PROP N
cores KEY Y
coresperchip PROP N
cpu PROP N
cpusorderable PROP N
hwavail PROP N
memory PROP N
opsys PROP N
other PROP N
processormhz KEY y
published PROP N
result RESULT Y
swavail PROP N
system KEY Y
testdate PROP N
testedby PROP N
updated PROP N
SPC-1
SPC-2
SPC-2_LDB
SPC-2_LFP
SPC-2_VOD
Storage Performance Council benchmarks company KEY Y
published PROP N
result RESULT Y
storconf PROP N
storcontroller KEY Y
stordisks KEY Y
storports KEY Y
storstreamused PROP N
stortech PROP N
system KEY Y
testdate PROP N
updated PROP N
TPC-C Transaction Processing Performance Council benchmarks company KEY Y
hwavail PROP N
opsys PROP N
other PROP N
published KEY Y
result KEY/RESULT Y
system KEY Y

Custom benchmark example

The following XML example loads an entry into the custom benchmark EX_CUSTOM_BENCH, used for the CPU.

<BENCHMARK_DATA>
<BENCHMARK>
<BENCHMARK_DEF BENCHMARK="EX_CUSTOM_BENCH" NAME="Custom benchmark example" DESCRIPTION="Custom CPU benchmark" APPLIESTO="CPU">
   <LABEL NAME="company" TYPE="KEY" MANDATORY="true"/>
   <LABEL NAME="system" TYPE="KEY" MANDATORY="true"/>
   <LABEL NAME="cores" TYPE="KEY" MANDATORY="true"/>
   <LABEL NAME="result" TYPE="RESULT" MANDATORY="true"/>
</BENCHMARK_DEF>
<BENCHMARK_RESULTS BENCHMARK="EX_CUSTOM_BENCH">
<BENCHMARK_ENTRY>
  <BENCHMARK_ENTRY_PROPS NAME="company" VALUE="MyTestCompany"/>
  <BENCHMARK_ENTRY_PROPS NAME="system" VALUE="MyTestSystem"/>
  <BENCHMARK_ENTRY_PROPS NAME="cores" VALUE="4"/>
  <BENCHMARK_ENTRY_PROPS NAME="result" VALUE="100"/>
</BENCHMARK_ENTRY>
</BENCHMARK_RESULTS>
</BENCHMARK>
</BENCHMARK_DATA>