Commit 66a3ad26 authored by Andrew McNab's avatar Andrew McNab
Browse files

DB12 in README

parent 548b6c6b
...@@ -12,14 +12,15 @@ https://repo.gridpp.ac.uk/machinejobfeatures/mjf-scripts/ ...@@ -12,14 +12,15 @@ https://repo.gridpp.ac.uk/machinejobfeatures/mjf-scripts/
1. Common configuration 1. Common configuration
2. Torque/PBS configuration 2. Torque/PBS configuration
3. HTCondor configuration 3. HTCondor configuration
4. DIRAC Benchmark (DB12)
1. Common configuration 1. Common configuration
----------------------- -----------------------
In the simplest case, just install the RPM and the /etc/rc.d/init.d/mjf In the simplest case, just install either Torque or HTCondor RPM and the
script will be run to create /etc/machinefeatures. $MACHINEFEATURES is /etc/rc.d/init.d/mjf script will be run to create /etc/machinefeatures.
set to this value by /etc/profile.d/mjf.sh and /etc/profile.d/mjf.csh which $MACHINEFEATURES is set to this value by /etc/profile.d/mjf.sh and
are (likely to be) sourced by new logins/jobs. /etc/profile.d/mjf.csh which are (likely to be) sourced by new logins/jobs.
The files /etc/sysconfig/mjf and /var/run/mjf are read when creating the The files /etc/sysconfig/mjf and /var/run/mjf are read when creating the
$MACHINEFEATURES (and $JOBFEATURES) directories, and can provide default $MACHINEFEATURES (and $JOBFEATURES) directories, and can provide default
...@@ -81,3 +82,34 @@ discover the number of logical processors HTCondor can allocated to jobs. ...@@ -81,3 +82,34 @@ discover the number of logical processors HTCondor can allocated to jobs.
This can be overriden by setting total_cpu in either mjf file. If the value This can be overriden by setting total_cpu in either mjf file. If the value
cannot otherwise by found, it is obtained by counting 'processor' lines in cannot otherwise by found, it is obtained by counting 'processor' lines in
/proc/cpuinfo. /proc/cpuinfo.
4. DIRAC Benchmark (DB12)
-------------------------
Support for the DIRAC fast benchmark (DB12) is also included, which is
implemented by analogy with HEPSPEC06: $MACHINEFEATURES/db12 and
$JOBFEATURES/db12_job are created if the DB12 measurements are available.
The key/value pairs db12 and db12_job can be included in /etc/sysconfig/mjf
or /var/run/mjf as with hs06 and hs06_job as described above.
However, it will normally be more convenient to create the file /etc/db12/db12
by simply installing the mjf-db12 RPM which runs the DB12 benchmark early in the
boot process when the machine is otherwise idle. The /etc/rc.d/init/db12 script
stores the result in /etc/db12/db12 along with /etc/db12/total_cpu, equal to the
number of DB12 benchmark instances run in parallel to make the measurement.
If /etc/db12/total_cpu exists before the db12 script is run, then it is used
to determine the number of instances to run. Otherwise the number of logical
processors is counted from the operating system and /etc/db12/total_cpu is
created.
Since /etc/rc.d/init.d/db12 is run very early in the boot process,
if /etc/db12/total_cpu is different from the number of logical processors,
then it must be created during the original installation (typically by Kickstart)
and not by subsequent configuration by a system such as Puppet which will be
started after db12 has run.
/etc/db12/total_cpu should match $MACHINEFEATURES/total_cpu so that the number of
DB12 instances run matches the number of processors available to be allocated to
jobs.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment