Difference between revisions of "Platform-releng-new-baseline"

From Eclipsepedia

Jump to: navigation, search
m (New page: <h4>Document to describe how to implement a new baseline once a release is available</h4> /home/users/releng/buildTools/eclipse.perf -bash-3.00$ -bash-3.00$ cp ref33.properties ref34.pro...)
 
m
 
(6 intermediate revisions by one user not shown)
Line 1: Line 1:
<h4>Document to describe how to implement a new baseline once a release is available</h4>
+
<h4>Document that describes how to implement a new baseline once a release is available</h4>
  
 +
<p>
 +
Branch the versions of org.eclipse.releng.basebuilder, org.eclipse.releng.eclipsebuilder, eclipseInternalBuildTools, eclipsePerformanceBuildTools and org.eclipse.releng to a name that indicates the new baseline - for example perf_33x
 +
</p>
  
 +
<p>Update ref.properties script on build machine.  With 3.4, we have pointed it to a new database - for example...</p>
 +
 +
<pre>net://trelenggtk.ottawa.ibm.com;dbname=perfDb34</pre>
 +
 +
 +
<pre>
 
/home/users/releng/buildTools/eclipse.perf
 
/home/users/releng/buildTools/eclipse.perf
 
-bash-3.00$
 
-bash-3.00$
 
-bash-3.00$ cp ref33.properties ref34.properties
 
-bash-3.00$ cp ref33.properties ref34.properties
 
-bash-3.00$ pwd
 
-bash-3.00$ pwd
 +
</pre>
 +
 +
<p>
 +
Update to ref34.properties in all.xml of eclipsePerfomanceBuildTools, and buildAll.xml of org.eclipse.releng.eclipsebuilder (both HEAD and perf_33x branch). 
 +
</p>
 +
 +
<p>
 +
Update HEAD version of org.eclipse.releng.eclipsebuilder/eclipse/sdk.tests/*perf/vm.properties to reference the new database and configuration as applicable.</p>
 +
 +
<p>Run new 3.3 baselines. Ensure that ref34.properties is updated after the baselines have completed so future builds have a baseline to compare against</p>
 +
 +
<strong>How to connect to the derby database from the command line</strong>
 +
 +
<pre>
 +
export JAVA_HOME=/builds/Cloudscape_10.0/ibm-jre-n142p/jre
 +
export DERBY_HOME=/builds/db-derby-10.4.2.0-bin
 +
export PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:$DERBY_HOME
 +
 +
cd /builds/db-derby-10.4.2.0-bin/bin
 +
 +
./ij
 +
 +
create the perfDb37 database
 +
 +
ij version 10.4
 +
ij> connect 'jdbc:derby:perfDb37;create=true';
 +
 +
 +
ij> protocol 'jdbc:derby';
 +
ij> connect to 'perfDb36';
 +
ij> show tables;
 +
ij> select * from guest.variation;
 +
 +
</pre>
 +
 +
Ensure that the vm.properties is the eclipse/buildsConfigs/sdk.tests/*/vm.properties refers to the new database name in both the HEAD and perf_36x branch.  In the 3.7 stream builds this is perfDb37.
 +
 +
Update the eclipsebuilder performance generation call to point to a new data directory on the build machine, for example data/v37 instead of data/v36.
 +
  
update to ref34.properties in all.xml of eclipsePerfomanceBuildTools
+
See [[http://db.apache.org/derby/papers/DerbyTut/ij_intro.html ij tutorial for more examples]]

Latest revision as of 13:52, 26 July 2010

Document that describes how to implement a new baseline once a release is available

Branch the versions of org.eclipse.releng.basebuilder, org.eclipse.releng.eclipsebuilder, eclipseInternalBuildTools, eclipsePerformanceBuildTools and org.eclipse.releng to a name that indicates the new baseline - for example perf_33x

Update ref.properties script on build machine. With 3.4, we have pointed it to a new database - for example...

net://trelenggtk.ottawa.ibm.com;dbname=perfDb34


/home/users/releng/buildTools/eclipse.perf
-bash-3.00$
-bash-3.00$ cp ref33.properties ref34.properties
-bash-3.00$ pwd

Update to ref34.properties in all.xml of eclipsePerfomanceBuildTools, and buildAll.xml of org.eclipse.releng.eclipsebuilder (both HEAD and perf_33x branch).

Update HEAD version of org.eclipse.releng.eclipsebuilder/eclipse/sdk.tests/*perf/vm.properties to reference the new database and configuration as applicable.

Run new 3.3 baselines. Ensure that ref34.properties is updated after the baselines have completed so future builds have a baseline to compare against

How to connect to the derby database from the command line

export JAVA_HOME=/builds/Cloudscape_10.0/ibm-jre-n142p/jre
export DERBY_HOME=/builds/db-derby-10.4.2.0-bin
export PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:$DERBY_HOME

cd /builds/db-derby-10.4.2.0-bin/bin

./ij

create the perfDb37 database

ij version 10.4
ij> connect 'jdbc:derby:perfDb37;create=true';


ij> protocol 'jdbc:derby';
ij> connect to 'perfDb36';
ij> show tables;
ij> select * from guest.variation;

Ensure that the vm.properties is the eclipse/buildsConfigs/sdk.tests/*/vm.properties refers to the new database name in both the HEAD and perf_36x branch. In the 3.7 stream builds this is perfDb37.

Update the eclipsebuilder performance generation call to point to a new data directory on the build machine, for example data/v37 instead of data/v36.


See [ij tutorial for more examples]