1402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll<contexts>
2402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll <context id="components" title="Components View">
3402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll    <description>This view shows the performance results in a hierarchical tree:
4402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael MollComponent
5402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll   + Scenario
6402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll      + Test machine
7402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll         + Build
8402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll            + Performance numbers
9402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll
10402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael MollTypically, the Eclipse builder runs performance tests for each component after the build is made on several performance test machines. Each component defines one or several specific performance test suites made of several test (aka scenario). Several performance numbers (e.g. Elapsed Process Time and CPU Time) are stored for each scenario and all build results are available in the performance results database.
11402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll
12402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael MollThis structure is roughly the same than the one used to generate performance results, hence make it easy to match the numbers in the corresponding page HTML page.</description>
13402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll </context>
14402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll <context id="builds" title="Builds view">
15402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll    <description>This view shows the list of all the builds contained in the connected database or in the local data files if no database is connected.
16402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll
17402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael MollDifferent fonts are used to display build names depending on the level of knowledge about the corresponding build:
18402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll - gray+italic: connected to a database but no available local data
19402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll - gray: connected to a database and local data do not contain any information for this build
20402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll - black: local data contain information about this build</description>
21402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll </context>
22402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll <context id="results" title="Component Results view">
23402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll    <description>This view show for each of the performance machine the entire results since the beginning.
24402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll
25402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael MollEach tab of this view represent a performance machine (also named config).
26402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael MollThe name of the machine is the name of the tab. The results are displayed in
27402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Molla table where each column represents a scenario and each line a build.
28402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael MollThe lines are ordered in descending order (from the most recent to the oldest build).</description>
29402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll </context>
30402794e73aed8611d62eb4b01cd155e2d76fcb87Raphael Moll</contexts>
31