Trace number 364525

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.107959

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-100-3_4-yes1-4.opb
MD5SUMd1d19e79916c7fd6bb39c96e6fa881fa
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.008998
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 clauses439
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1
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 2
Number of bits of the biggest number in a constraint 2
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 x6 x8 x9 x12 x14 x16 x17 x19 x22 x23 x26 x27 x30 x31 x33 x36 x38 x40 x42 x44 x45 x47 x50 x52 x54 x56 x57 x59 x62 x63 x66 x67 x69 x72
0.06/0.10	v x74 x76 x77 x79 x81 x83 x86 x87 x90 x91 x94 x95 x97 x99 x101 x103 x106 x107 x110 x111 x113 x116 x117 x119 x121 x124 x126 x127 x129
0.06/0.10	v x131 x134 x135 x138 x139 x141 x143 x146 x147 x149 x151 x153 x156 x157 x160 x162 x163 x165 x168 x170 x172 x173 x176 x177 x179 x181
0.06/0.10	v x184 x186 x187 x190 x192 x194 x195 x197 x199

Verifier Data (download as text)

OK	100

Conversion Script Data (download as text)

/tmp/evaluation/364525-1177040815/instance-364525-1177040815.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/node69/watcher-364525-1177040815 -o ROOT/results/node69/solver-364525-1177040815 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-364525-1177040815.opb /tmp/evaluation/364525-1177040815/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.81 0.95 0.98 2/64 26281
/proc/meminfo: memFree=1771004/2055920 swapFree=4182908/4192956
[pid=26281] ppid=26279 vsize=12268 CPUtime=0
/proc/26281/stat : 26281 (pbclasp) R 26279 26281 26198 0 -1 4194304 395 0 0 0 0 0 0 0 18 0 1 0 180070964 12562432 361 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 237947491041 0 0 4224 0 0 0 0 17 1 0 0
/proc/26281/statm: 3067 361 275 3 0 167 0

[startup+0.083506 s]
/proc/loadavg: 0.81 0.95 0.98 2/64 26281
/proc/meminfo: memFree=1771004/2055920 swapFree=4182908/4192956
[pid=26281] ppid=26279 vsize=12400 CPUtime=0.05
/proc/26281/stat : 26281 (pbclasp) S 26279 26281 26198 0 -1 4194304 685 2517 0 0 0 0 4 1 16 0 1 0 180070964 12697600 477 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 237956546452 0 0 4231 16384 18446744071563356171 0 0 17 1 0 0
/proc/26281/statm: 3100 477 343 3 0 200 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 12400

[startup+0.101505 s]
/proc/loadavg: 0.81 0.95 0.98 2/64 26281
/proc/meminfo: memFree=1771004/2055920 swapFree=4182908/4192956
[pid=26281] ppid=26279 vsize=12400 CPUtime=0.06
/proc/26281/stat : 26281 (pbclasp) S 26279 26281 26198 0 -1 4194304 716 3321 0 0 0 0 5 1 16 0 1 0 180070964 12697600 477 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 237956546452 0 0 4230 16384 18446744071563356171 0 0 17 1 0 0
/proc/26281/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.107959
CPU time (s): 0.102983
CPU user time (s): 0.069989
CPU system time (s): 0.032994
CPU usage (%): 95.3908
Max. virtual memory (cumulated for all children) (KiB): 12400

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.069989
system time used= 0.032994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5099
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= 134
involuntary context switches= 20

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node69 on Fri Apr 20 03:46:55 UTC 2007

IDJOB= 364525
IDBENCH= 2125
IDSOLVER= 167
FILE ID= node69/364525-1177040815

PBS_JOBID= 4640130

Free space on /tmp= 66498 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-4.opb
COMMAND LINE= pbclasp instance-364525-1177040815.opb /tmp/evaluation/364525-1177040815/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node69/convwatcher-364525-1177040815 -o ROOT/results/node69/conversion-364525-1177040815 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/364525-1177040815/instance-364525-1177040815.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  d1d19e79916c7fd6bb39c96e6fa881fa

RANDOM SEED= 709729844

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node69.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.264
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	: 5931.00
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.264
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:       1771604 kB
Buffers:         43964 kB
Cached:         177024 kB
SwapCached:       3888 kB
Active:          79488 kB
Inactive:       151140 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1771604 kB
SwapTotal:     4192956 kB
SwapFree:      4182908 kB
Dirty:             676 kB
Writeback:           0 kB
Mapped:          15192 kB
Slab:            39692 kB
Committed_AS:  2144488 kB
PageTables:       1472 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= 66498 MiB

End job on node69 on Fri Apr 20 03:46:56 UTC 2007