<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://t2bwiki.iihe.ac.be/index.php?action=history&amp;feed=atom&amp;title=Workernode-v0.0.1</id>
	<title>Workernode-v0.0.1 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://t2bwiki.iihe.ac.be/index.php?action=history&amp;feed=atom&amp;title=Workernode-v0.0.1"/>
	<link rel="alternate" type="text/html" href="https://t2bwiki.iihe.ac.be/index.php?title=Workernode-v0.0.1&amp;action=history"/>
	<updated>2026-05-16T10:36:36Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://t2bwiki.iihe.ac.be/index.php?title=Workernode-v0.0.1&amp;diff=365&amp;oldid=prev</id>
		<title>Maintenance script: Created page with &quot; === Basic System Installation === The basic requirements for this benchmark is to have RHEL ES 4.3 for the x86_64 architecture installed and running on the hardware. The RHEL...&quot;</title>
		<link rel="alternate" type="text/html" href="https://t2bwiki.iihe.ac.be/index.php?title=Workernode-v0.0.1&amp;diff=365&amp;oldid=prev"/>
		<updated>2015-08-26T12:29:31Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot; === Basic System Installation === The basic requirements for this benchmark is to have RHEL ES 4.3 for the x86_64 architecture installed and running on the hardware. The RHEL...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&lt;br /&gt;
=== Basic System Installation ===&lt;br /&gt;
The basic requirements for this benchmark is to have RHEL ES 4.3 for the x86_64 architecture installed and running on the hardware.&lt;br /&gt;
The RHEL4 clones CentOS 4.3 http://www.centos.org/ and Scientific Linux 4.3 https://www.scientificlinux.org/ are also valid for the benchmark. We even recommand one of those clones because they provide yum (updater and package installer which is used below) by default. &lt;br /&gt;
Installation instructions can be found on the sites or are provide with the copy.&lt;br /&gt;
&lt;br /&gt;
All benchmarks will be run in 64-bit mode. In order to complete the benchmarks succesfully, a number of compatibility rpms have to be installed on the system.&lt;br /&gt;
&lt;br /&gt;
Starting from a standard Desktop installation, install the following rpms (.i386 and .x86_64 indicate the rpms for both architecture versions) and their corresponding dependencies. (This is easiest done using yum.): &lt;br /&gt;
  yum install libf2c.i386 libf2c.x86_64 openmotif.i386 openmotif.x86_64 xorg-x11-Mesa-libGLU.i386 xorg-x11-Mesa-libGLU.x86_64&lt;br /&gt;
  yum install compat-libstdc++-33-3.2.3-47.3&lt;br /&gt;
==== Partition and Filesystem setup ====&lt;br /&gt;
In order to run the benchmark succesfully, there must be approximately 4GB free diskspace on one partition. We advise to use ext3 as filesystem. No further requirements are needed.&lt;br /&gt;
=== CMS benchmark ===&lt;br /&gt;
Make sure the machine is connected to the internet. Run as root: &lt;br /&gt;
  wget -q http://nahi.iihe.ac.be/run_cmsbench-4.sh -O run_cmsbench-4.sh;chmod +x run_cmsbench-4.sh;./run_cmsbench-4.sh 4&lt;br /&gt;
&lt;br /&gt;
The benchmark consists of a script that will&lt;br /&gt;
# download the necessary software in one single tarball (approximately 650MB. It might take a while to download.)&lt;br /&gt;
# extract the tarball and install the software&lt;br /&gt;
# run all benchmarks&lt;br /&gt;
# printout the numbers&lt;br /&gt;
# create a tarball with detailed results.&lt;br /&gt;
&lt;br /&gt;
Running the application benchmark itself takes at most 6 hours and requires&lt;br /&gt;
no manual intervention. At the end, a number will be printed on screen indicating&lt;br /&gt;
the relative performance of the system. Also a file with a detailed description&lt;br /&gt;
of the system used and detailed results of all the tests will be provided.&lt;br /&gt;
&lt;br /&gt;
When the script ran successfully, it will print out something like &lt;br /&gt;
 Running test from directory /benchmark&lt;br /&gt;
  /benchmark/cms&lt;br /&gt;
   Now timing 1 single Root stress test:&lt;br /&gt;
   Now timing 1 single Root stressgeom test:&lt;br /&gt;
   Now timing 1 single Root stressLinear test:&lt;br /&gt;
   Now timing 1 single Root bench test:&lt;br /&gt;
   Now timing 4 simultaneous root stress runs:&lt;br /&gt;
  Exit code 0&lt;br /&gt;
   Now timing 1 single Pythia stress test:&lt;br /&gt;
   Now timing 4 simultaneous pythia stress runs:&lt;br /&gt;
  Exit code 0&lt;br /&gt;
   ATTENTION !!! All environment variables &lt;br /&gt;
   matching pattern  *_PATH will be unset !!!&lt;br /&gt;
   Now timing 1 single oscar run:&lt;br /&gt;
&lt;br /&gt;
 ...&lt;br /&gt;
&lt;br /&gt;
   1guest249.fynu.ucl.ac.be/64/stress1.txt , 0&lt;br /&gt;
   Gold1 1288.3&lt;br /&gt;
   1guest249.fynu.ucl.ac.be/64/stress2.txt , 0&lt;br /&gt;
   Gold2 1291.4&lt;br /&gt;
   1guest249.fynu.ucl.ac.be/64/stress3.txt , 0&lt;br /&gt;
   Gold3 1285.2&lt;br /&gt;
   1guest249.fynu.ucl.ac.be/64/stress4.txt , 0&lt;br /&gt;
   Gold4 1292.8&lt;br /&gt;
      Res64 0: 1.0901462631045&lt;br /&gt;
   1guest249.fynu.ucl.ac.be/64/timesusy1.txt , 1&lt;br /&gt;
   Gold1 135.488503800453&lt;br /&gt;
   1guest249.fynu.ucl.ac.be/64/timesusy2.txt , 1&lt;br /&gt;
   Gold2 135.50135501355&lt;br /&gt;
   1guest249.fynu.ucl.ac.be/64/timesusy3.txt , 1&lt;br /&gt;
   Gold3 135.699940292026&lt;br /&gt;
   1guest249.fynu.ucl.ac.be/64/timesusy4.txt , 1&lt;br /&gt;
   Gold4 135.587704906919&lt;br /&gt;
      Res64 1: 1.10156314295309&lt;br /&gt;
   Relative strength of this box: Res= 4.78483211009748&lt;br /&gt;
   Relative 32 to 64= 1.03331347491351&lt;br /&gt;
   32 to 64= 1.2876476914783&lt;br /&gt;
&lt;br /&gt;
The number indicating the relative performance of the system is found at the line biginning by: &amp;quot;Relative strength of this box: Res=&amp;quot;.&lt;br /&gt;
The file with the detailed results is the zipped file created in the directory where the script was executed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{TracNotice|{{PAGENAME}}}}&lt;/div&gt;</summary>
		<author><name>Maintenance script</name></author>
	</entry>
</feed>