Trace number 364483

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-clasp 2007-04-10OPT100 0.102983 0.108721

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-100-3_4-yes1-3.opb
MD5SUM577b644759bfadb428b7642b44c91218
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark100
Best CPU time to get the best result obtained on this benchmark0.008997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 100
Optimality of the best value was proved YES
Number of variables200
Total number of constraints440
Number of constraints which are clauses440
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint3
Number of terms in the objective function 200
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 200
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 200
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

Solver Data (download as text)

0.00/0.07	o 100
0.06/0.10	s OPTIMUM FOUND
0.06/0.10	v x2 x3 x5 x8 x9 x11 x13 x15 x17 x20 x21 x24 x26 x27 x29 x31 x34 x36 x38 x39 x42 x43 x46 x47 x49 x52 x53 x55 x57 x59 x61 x63 x66 x67 x70 x72
0.06/0.10	v x73 x75 x78 x79 x82 x83 x86 x88 x89 x92 x93 x95 x97 x100 x101 x103 x106 x107 x109 x112 x114 x115 x117 x119 x121 x124 x126 x128 x129
0.06/0.10	v x131 x134 x136 x137 x140 x141 x143 x145 x148 x150 x151 x154 x156 x158 x159 x162 x163 x165 x168 x169 x172 x173 x176 x177 x180 x181
0.06/0.10	v x183 x185 x188 x190 x191 x193 x195 x197 x200

Verifier Data (download as text)

OK	100

Conversion Script Data (download as text)

/tmp/evaluation/364483-1177040573/instance-364483-1177040573.opb is already a linear file

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node38/watcher-364483-1177040573 -o ROOT/results/node38/solver-364483-1177040573 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-364483-1177040573.opb /tmp/evaluation/364483-1177040573/temp 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.91 0.95 0.97 3/77 4061
/proc/meminfo: memFree=1697152/2055920 swapFree=4159716/4192956
[pid=4061] ppid=4059 vsize=12268 CPUtime=0
/proc/4061/stat : 4061 (pbclasp) R 4059 4061 3831 0 -1 4194304 351 0 0 0 0 0 0 0 18 0 1 0 136224005 12562432 317 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 266890607205 0 0 4224 0 0 0 0 17 1 0 0
/proc/4061/statm: 3067 317 242 3 0 167 0

[startup+0.0265711 s]
/proc/loadavg: 0.91 0.95 0.97 3/77 4061
/proc/meminfo: memFree=1697152/2055920 swapFree=4159716/4192956
[pid=4061] ppid=4059 vsize=12400 CPUtime=0
/proc/4061/stat : 4061 (pbclasp) S 4059 4061 3831 0 -1 4194304 497 0 0 0 0 0 0 0 16 0 1 0 136224005 12697600 450 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 266899337314 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/4061/statm: 3100 450 324 3 0 200 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12400

[startup+0.101586 s]
/proc/loadavg: 0.91 0.95 0.97 3/77 4061
/proc/meminfo: memFree=1697152/2055920 swapFree=4159716/4192956
[pid=4061] ppid=4059 vsize=12400 CPUtime=0.06
/proc/4061/stat : 4061 (pbclasp) S 4059 4061 3831 0 -1 4194304 717 3321 0 0 0 0 4 2 16 0 1 0 136224005 12697600 477 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 266899341204 0 0 4230 16384 18446744071563356171 0 0 17 1 0 0
/proc/4061/statm: 3100 477 343 3 0 200 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 12400

Solver just ended. Dumping a history of the last processes samples

Child status: 0
Real time (s): 0.108721
CPU time (s): 0.102983
CPU user time (s): 0.065989
CPU system time (s): 0.036994
CPU usage (%): 94.7223
Max. virtual memory (cumulated for all children) (KiB): 12400

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.065989
system time used= 0.036994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5101
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 144
involuntary context switches= 24

runsolver used 0.000999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node38 on Fri Apr 20 03:42:53 UTC 2007

IDJOB= 364483
IDBENCH= 2118
IDSOLVER= 167
FILE ID= node38/364483-1177040573

PBS_JOBID= 4640122

Free space on /tmp= 66243 MiB

SOLVER NAME= PB-clasp 2007-03-23
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-100-3_4-yes1-3.opb
COMMAND LINE= pbclasp instance-364483-1177040573.opb /tmp/evaluation/364483-1177040573/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node38/convwatcher-364483-1177040573 -o ROOT/results/node38/conversion-364483-1177040573 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/364483-1177040573/instance-364483-1177040573.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node38/watcher-364483-1177040573 -o ROOT/results/node38/solver-364483-1177040573 -C 1800 -W 3600 -M 1800 --output-limit 1,15  pbclasp instance-364483-1177040573.opb /tmp/evaluation/364483-1177040573/temp

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  577b644759bfadb428b7642b44c91218

RANDOM SEED= 714323569

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node38.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.263
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	: 5914.62
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.263
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	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1697624 kB
Buffers:         36408 kB
Cached:         234260 kB
SwapCached:       3100 kB
Active:         121088 kB
Inactive:       174036 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1697624 kB
SwapTotal:     4192956 kB
SwapFree:      4159716 kB
Dirty:             664 kB
Writeback:           0 kB
Mapped:          32680 kB
Slab:            48440 kB
Committed_AS:  1555980 kB
PageTables:       2060 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66243 MiB

End job on node38 on Fri Apr 20 03:42:54 UTC 2007