Home | History | Annotate | Download | only in html 
      1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
      2 
      3 <html>
      4 <head>
      5 	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
      6 	<title>Overview</title>
      7 </head>
      8 
      9 <body>
     10 <h1>Overview</h1>
     11 The performance results tool provide an easy way to look at results collected
     12 while running performance tests on a build. It is accessible using the <b>Performance Results</b>
     13 perspective:
     14 <p><img src="images/perspective.png" alt="Performance Results perspective"/></p>
     15 <p>
     16 There are 4 views in this perspective:
     17 <ul>
     18 <li><a href="components.html">Components view</a>: This is the view to see
     19 the results in details for each components</li>
     20 <li><a href="builds.html">Builds view</a>: This is the view to see all builds,
     21 update local data and generate results when necessary</li>
     22 <li><a href="results.html">Components Results view</a>: This is the view to
     23 see whole results for each machine in a single table</li>
     24 <li><a href="properties.html">Properties view</a>: Display element properties
     25 (typically results numbers and other database information)</li>
     26 </ul>
     27 </p><p>
     28 The goal of this tool is both to look at performance results database numbers
     29 and to verify whether a build result may have scenario showing performance regression.
     30 </p><p>
     31 The view to use to look at performance results number is the <a href="components.html">Components view</a>.
     32 In this results are displayed in a hierarchical tree which have a similar structure
     33 than the generated HTML pages (e.g.
     34 <a href="http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/performance/performance.php">Eclipse 3.5.0</a>).
     35 The complete performance results information is provided on each element of the tree in the
     36 <a href="properties.html">Properties view</a>. This is typically useful when a scenario
     37 results looks weird to have the ability to verify that the numbers looks correct
     38 or not.
     39 </p><p>
     40 The view to verify whether a regression occurs is the <a href="results.html">Components Results view</a>.
     41 All results for one component are shown in a single table which also provides
     42 all necessary information to decide whether a noticed regression could be confirmed
     43 or not.
     44 </p>
     45 </body>
     46 </html>