Trace number 372376

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-10OPT5867 0.168973 0.205247

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-LIN/submittedPB07/
poldner/PB/testset/normalized-6_12.opb
MD5SUMd3b3d1e364c50657a7515a2e4087a65b
Bench CategoryOPT-SMALLINT-LIN (optimisation, small integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark5867
Best CPU time to get the best result obtained on this benchmark0.006998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 5867
Optimality of the best value was proved YES
Number of variables78
Total number of constraints84
Number of constraints which are clauses72
Number of constraints which are cardinality constraints (but not clauses)12
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint6
Number of terms in the objective function 78
Biggest coefficient in the objective function 2194
Number of bits for the biggest coefficient in the objective function 12
Sum of the numbers in the objective function 39785
Number of bits of the sum of numbers in the objective function 16
Biggest number in a constraint 2194
Number of bits of the biggest number in a constraint 12
Biggest sum of numbers in a constraint 39785
Number of bits of the biggest sum of numbers16
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/0.04	o 6412
0.00/0.06	o 6400
0.00/0.09	o 6160
0.07/0.14	o 5867
0.14/0.20	s OPTIMUM FOUND
0.14/0.20	v x2 x8 x14 x20 x26 x32 x38 x44 x50 x56 x62 x68 x74

Verifier Data (download as text)

OK	5867

Conversion Script Data (download as text)

/tmp/evaluation/372376-1177092567/instance-372376-1177092567.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/node23/watcher-372376-1177092567 -o ROOT/results/node23/solver-372376-1177092567 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-372376-1177092567.opb /tmp/evaluation/372376-1177092567/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.92 0.97 0.99 3/77 19723
/proc/meminfo: memFree=1755360/2055920 swapFree=4169120/4192956
[pid=19723] ppid=19721 vsize=12268 CPUtime=0
/proc/19723/stat : 19723 (pbclasp) R 19721 19723 18466 0 -1 4194304 351 0 0 0 0 0 0 0 18 0 1 0 157173810 12562432 317 18446744073709551615 4194304 4206940 548682069216 18446744073709551615 238496562174 0 0 4224 0 0 0 0 17 1 0 0
/proc/19723/statm: 3067 317 242 3 0 167 0

[startup+0.0987951 s]
/proc/loadavg: 0.92 0.97 0.99 3/77 19723
/proc/meminfo: memFree=1755360/2055920 swapFree=4169120/4192956
[pid=19723] ppid=19721 vsize=12400 CPUtime=0.06
/proc/19723/stat : 19723 (pbclasp) S 19721 19723 18466 0 -1 4194304 894 5869 0 0 0 0 3 3 16 0 1 0 157173810 12697600 467 18446744073709551615 4194304 4206940 548682069216 18446744073709551615 238496559202 0 0 4224 16384 18446744071563648864 0 0 17 0 0 0
/proc/19723/statm: 3100 467 343 3 0 200 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 12400

[startup+0.101794 s]
/proc/loadavg: 0.92 0.97 0.99 3/77 19723
/proc/meminfo: memFree=1755360/2055920 swapFree=4169120/4192956
[pid=19723] ppid=19721 vsize=12400 CPUtime=0.07
/proc/19723/stat : 19723 (pbclasp) S 19721 19723 18466 0 -1 4194304 913 6272 0 0 0 0 3 4 16 0 1 0 157173810 12697600 467 18446744073709551615 4194304 4206940 548682069216 18446744073709551615 238496559202 0 0 4224 16384 18446744071563648864 0 0 17 0 0 0
/proc/19723/statm: 3100 467 343 3 0 200 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 12400

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

[startup+0.201816 s]
/proc/loadavg: 0.92 0.97 0.99 3/77 19723
/proc/meminfo: memFree=1755360/2055920 swapFree=4169120/4192956
[pid=19723] ppid=19721 vsize=12400 CPUtime=0.14
/proc/19723/stat : 19723 (pbclasp) R 19721 19723 18466 0 -1 4194304 1049 9162 0 0 0 1 8 5 16 0 1 0 157173810 12697600 467 18446744073709551615 4194304 4206940 548682069216 18446744073709551615 238496562174 0 0 4224 16384 0 0 0 17 0 0 0
/proc/19723/statm: 3100 467 343 3 0 200 0
Current children cumulated CPU time (s) 0.14
Current children cumulated vsize (KiB) 12400

Child status: 0
Real time (s): 0.205247
CPU time (s): 0.168973
CPU user time (s): 0.095985
CPU system time (s): 0.072988
CPU usage (%): 82.3266
Max. virtual memory (cumulated for all children) (KiB): 12400

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.095985
system time used= 0.072988
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 10425
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= 299
involuntary context switches= 50

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node23 on Fri Apr 20 18:09:27 UTC 2007

IDJOB= 372376
IDBENCH= 24967
IDSOLVER= 167
FILE ID= node23/372376-1177092567

PBS_JOBID= 4640324

Free space on /tmp= 66455 MiB

SOLVER NAME= PB-clasp 2007-03-23
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-LIN/submittedPB07/poldner/PB/testset/normalized-6_12.opb
COMMAND LINE= pbclasp instance-372376-1177092567.opb /tmp/evaluation/372376-1177092567/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node23/convwatcher-372376-1177092567 -o ROOT/results/node23/conversion-372376-1177092567 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/372376-1177092567/instance-372376-1177092567.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  d3b3d1e364c50657a7515a2e4087a65b

RANDOM SEED= 556113528

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node23.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.276
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.276
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:       1755768 kB
Buffers:         56556 kB
Cached:         152304 kB
SwapCached:       2552 kB
Active:         138072 kB
Inactive:        94692 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1755768 kB
SwapTotal:     4192956 kB
SwapFree:      4169120 kB
Dirty:             704 kB
Writeback:           0 kB
Mapped:          30492 kB
Slab:            52944 kB
Committed_AS:  2738404 kB
PageTables:       1796 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= 66455 MiB

End job on node23 on Fri Apr 20 18:09:27 UTC 2007