Trace number 46654

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerObjective functionCPU timeWall clock time
PB-smodels 1.31OPT11 0.083987 0.0731131

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB06/manquiho/golomb-rulers/normalized-OGR_5.opb
MD5SUMf7ce1bbc714a6b404586716e62ae4fc9
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark11
Best CPU time to get the best result obtained on this benchmark0.010998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 11
Optimality of the best value was proved YES
Number of variables75
Total number of constraints104
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints104
Minimum length of a constraint10
Maximum length of a constraint21
Number of terms in the objective function 5
Biggest coefficient in the objective function 16
Number of bits for the biggest coefficient in the objective function 5
Sum of the numbers in the objective function 31
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 32
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 173
Number of bits of the biggest sum of numbers8
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.00	c Running pbsmodels-v1.31
0.04	o 14
0.05	o 12
0.06	o 11
0.06	s OPTIMUM FOUND
0.06	v x1 x2 x4 x16 x17 x18 x24 x75 x7 x67 x63 x61 x60 x58 x57 x56 x53 x52 x48 x46 x45 x44 x43 x41 x40 x39 x38 x37 x36 x35 x34 x33 x32 x31 x30
0.06	v x29 x28 x27 x26 -x3 -x5 -x19 -x20 -x21 -x22 -x23 -x25 -x6 -x8 -x9 -x10 -x74 -x73 -x72 -x71 -x70 -x11 -x12 -x13 -x14 -x15 -x69 -x68
0.06	v -x66 -x65 -x64 -x62 -x59 -x55 -x54 -x51 -x50 -x49 -x47 -x42

Verifier Data (download as text)

OK	11

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes

runsolver version 3.0.1 (c) roussel@cril.univ-artois.fr

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node79/watcher-46654-1149782442 -o ROOT/results/node79/solver-46654-1149782442 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node79/46654-1149782442/instance-46654-1149782442.opb 267753551 ROOT/tmp/node79/46654-1149782442 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.72 0.93 0.93 2/67 9811
/proc/meminfo: memFree=1753376/2055892 swapFree=4085412/4096564
[pid=9811] ppid=9809 vsize=5368 CPUtime=0
/proc/9811/stat : 9811 (runpbsmodels) S 9809 9811 9765 0 -1 4194304 285 0 0 0 0 0 0 0 20 0 1 0 243882861 5496832 233 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 241011583556 0 65536 4100 65538 18446744071563358023 0 0 17 0 0 0
/proc/9811/statm: 1342 233 194 169 0 52 0
[pid=9812] ppid=9811 vsize=12136 CPUtime=0
/proc/9812/stat : 9812 (pbsmodels-v1.31) R 9811 9811 9765 0 -1 4194304 270 0 0 0 0 0 0 0 21 0 1 0 243882862 12427264 236 18446744073709551615 4194304 4206940 548682069024 18446744073709551615 241020483922 0 0 4224 0 0 0 0 17 0 0 0
/proc/9812/statm: 3034 236 179 3 0 133 0

Child status: 0
Real time (s): 0.0731131
CPU time (s): 0.083987
CPU user time (s): 0.06499
CPU system time (s): 0.018997
CPU usage (%): 114.873
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node79 on Thu Jun  8 16:00:42 UTC 2006


FILE ID= 46654-1149782442

PBS_JOBID= 373086

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/golomb-rulers/normalized-OGR_5.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node79/46654-1149782442/instance-46654-1149782442.opb 267753551  ROOT/tmp/node79/46654-1149782442
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node79/watcher-46654-1149782442 -o ROOT/results/node79/solver-46654-1149782442 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node79/46654-1149782442/instance-46654-1149782442.opb 267753551  ROOT/tmp/node79/46654-1149782442

MD5SUM SOLVER= 95562bc622ddb1f976359072aec5ad24 7fcd858753252b26b88f3383e979819a c732bc4c3aeda9195daa74a308a1f78e b7e54d975d35ab28450b6de5c14d303e f7da3270b2cd5190fa0cd9af9b854ca4
MD5SUM BENCH=  f7ce1bbc714a6b404586716e62ae4fc9

RANDOM SEED= 267753551


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.234
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6006.18
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.234
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1753584 kB
Buffers:         32132 kB
Cached:         208316 kB
SwapCached:       2448 kB
Active:          96920 kB
Inactive:       152344 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1753584 kB
SwapTotal:     4096564 kB
SwapFree:      4085412 kB
Dirty:             272 kB
Writeback:           0 kB
Mapped:          16560 kB
Slab:            39680 kB
Committed_AS:   434356 kB
PageTables:       1304 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node79 on Thu Jun  8 16:00:43 UTC 2006