Benchmarking: CPUBurn-in - Revision history

Jon: /* Install Libraries */

2013-01-09T16:09:12Z

Install Libraries

2013-01-09T16:07:02Z

2012-09-21T13:38:56Z

Ending CPUBurn-in

2012-09-17T09:47:46Z

2012-09-17T09:45:00Z

Run CPUBurn-in

@@ Line 5: / Line 5: @@
 == Install Libraries ==
 <syntaxhighlight>
 [root@node1 ~]#yum -y install glibc.i686

@@ Line 36: / Line 36: @@
 == Ending CPUBurn-in ==
-To kill cpuburn-in manually before the states completion time, use <code>killall</code>:
+To kill cpuburn-in manually before the stated completion time, use <code>killall</code>:
 <syntaxhighlight>
 [root@raldisk ~]# killall cpuburn-in
 </syntaxhighlight>

← Older revision		Revision as of 09:47, 17 September 2012
Line 33:		Line 33:

	NB - the "3600" above is the number of seconds for the stress test to run.		NB - the "3600" above is the number of seconds for the stress test to run.
		+
		+	== Ending CPUBurn-in ==
		+
		+	To kill cpuburn-in manually before the states completion time, use <code>killall</code>:
		+	<syntaxhighlight>
		+	[root@raldisk ~]# killall cpuburn-in
		+	</syntaxhighlight>

@@ Line 3: / Line 3: @@
 CPUBurn-in files can be obtained from:
 <code>//storage1/software/hpc/benchmarks/cpuburn-in/cpuburn-in.tar.gz</code>
 == Extract CPUBurn-in ==
 <syntaxhighlight>
 [root@raldisk ~]# tar zxvf cpuburn-in.tar.gz

@@ Line 14: / Line 14: @@
 == Run CPUBurn-in ==
-It may be necessary to <code>chmod</code> the extracted binary to run (or execute the binary with <code>sh</code>:
+It may be necessary to <code>chmod</code> the extracted binary to run (or execute the binary with <code>sh</code>):
 <syntaxhighlight>
 [root@raldisk ~]# chmod +x cpuburn-in