Trace number 363573

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-10OPT3089 0.138978 0.148185

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/mps-v2-20-10/
MIPLIB/miplib/normalized-mps-v2-20-10-p0033.opb
MD5SUMbdb886a987b9ca760f19a56a745e3c06
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3089
Best CPU time to get the best result obtained on this benchmark0.016996
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3089
Optimality of the best value was proved YES
Number of variables33
Total number of constraints15
Number of constraints which are clauses1
Number of constraints which are cardinality constraints (but not clauses)3
Number of constraints which are nor clauses,nor cardinality constraints11
Minimum length of a constraint2
Maximum length of a constraint19
Number of terms in the objective function 33
Biggest coefficient in the objective function 517
Number of bits for the biggest coefficient in the objective function 10
Sum of the numbers in the objective function 7276
Number of bits of the sum of numbers in the objective function 13
Biggest number in a constraint 1656
Number of bits of the biggest number in a constraint 11
Biggest sum of numbers in a constraint 7276
Number of bits of the biggest sum of numbers13
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.03	o 3966
0.02/0.05	o 3707
0.02/0.07	o 3457
0.02/0.09	o 3302
0.07/0.11	o 3089
0.07/0.14	s OPTIMUM FOUND
0.07/0.14	v x1 x7 x8 x10 x14 x19 x20 x23 x25 x26 x27 x28 x29 x30

Verifier Data (download as text)

OK	3089

Conversion Script Data (download as text)

/tmp/evaluation/363573-1177029527/instance-363573-1177029527.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/node26/watcher-363573-1177029527 -o ROOT/results/node26/solver-363573-1177029527 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-363573-1177029527.opb /tmp/evaluation/363573-1177029527/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.95 0.98 0.99 3/77 31923
/proc/meminfo: memFree=1687648/2055920 swapFree=4170240/4192956
[pid=31923] ppid=31921 vsize=12268 CPUtime=0
/proc/31923/stat : 31923 (pbclasp) R 31921 31923 31299 0 -1 4194304 398 0 0 0 0 0 0 0 18 0 1 0 150869539 12562432 364 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 269028332257 0 0 4224 0 0 0 0 17 1 0 0
/proc/31923/statm: 3067 365 276 3 0 167 0

[startup+0.0497889 s]
/proc/loadavg: 0.95 0.98 0.99 3/77 31923
/proc/meminfo: memFree=1687648/2055920 swapFree=4170240/4192956
[pid=31923] ppid=31921 vsize=12400 CPUtime=0.02
/proc/31923/stat : 31923 (pbclasp) S 31921 31923 31299 0 -1 4194304 675 2851 0 0 0 0 1 1 16 0 1 0 150869539 12697600 463 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 269037387668 0 0 4231 16384 18446744071563356171 0 0 17 0 0 0
/proc/31923/statm: 3100 463 343 3 0 200 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 12400

[startup+0.102786 s]
/proc/loadavg: 0.95 0.98 0.99 3/77 31923
/proc/meminfo: memFree=1687648/2055920 swapFree=4170240/4192956
[pid=31923] ppid=31921 vsize=12400 CPUtime=0.07
/proc/31923/stat : 31923 (pbclasp) S 31921 31923 31299 0 -1 4194304 991 7479 0 0 0 0 3 4 16 0 1 0 150869539 12697600 463 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 269037383778 0 0 4224 16384 18446744071563648864 0 0 17 0 0 0
/proc/31923/statm: 3100 463 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

Child status: 0
Real time (s): 0.148185
CPU time (s): 0.138978
CPU user time (s): 0.051992
CPU system time (s): 0.086986
CPU usage (%): 93.7868
Max. virtual memory (cumulated for all children) (KiB): 12400

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.051992
system time used= 0.086986
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 12090
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= 334
involuntary context switches= 53

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node26 on Fri Apr 20 00:38:47 UTC 2007

IDJOB= 363573
IDBENCH= 1863
IDSOLVER= 167
FILE ID= node26/363573-1177029527

PBS_JOBID= 4630631

Free space on /tmp= 66436 MiB

SOLVER NAME= PB-clasp 2007-03-23
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/mps-v2-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-p0033.opb
COMMAND LINE= pbclasp instance-363573-1177029527.opb /tmp/evaluation/363573-1177029527/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node26/convwatcher-363573-1177029527 -o ROOT/results/node26/conversion-363573-1177029527 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/363573-1177029527/instance-363573-1177029527.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  bdb886a987b9ca760f19a56a745e3c06

RANDOM SEED= 479110997

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node26.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.213
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.213
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:       1688056 kB
Buffers:         38544 kB
Cached:         241956 kB
SwapCached:       3128 kB
Active:         119664 kB
Inactive:       184072 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1688056 kB
SwapTotal:     4192956 kB
SwapFree:      4170240 kB
Dirty:             696 kB
Writeback:           0 kB
Mapped:          30844 kB
Slab:            49600 kB
Committed_AS:  1042856 kB
PageTables:       1716 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= 66436 MiB

End job on node26 on Fri Apr 20 00:38:48 UTC 2007