Trace number 364152

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-03-23UNSAT 0.78088 0.783449

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-bf0432-007.opb
MD5SUM093787cffe9173c370b11fb5e77a5812
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkUNSAT
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark0.087985
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables2080
Total number of constraints4708
Number of constraints which are clauses4708
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 constraint1
Maximum length of a constraint6
Number of terms in the objective function 2080
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 2080
Number of bits of the sum of numbers in the objective function 12
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 2080
Number of bits of the biggest sum of numbers12
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.39/0.78	s UNSATISFIABLE

Verifier Data (download as text)

ERROR: no interpretation found !

Conversion Script Data (download as text)

/tmp/evaluation/364152-1177037466/instance-364152-1177037466.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/node66/watcher-364152-1177037466 -o ROOT/results/node66/solver-364152-1177037466 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-364152-1177037466.opb /tmp/evaluation/364152-1177037466/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.98 0.99 3/64 20416
/proc/meminfo: memFree=1813672/2055920 swapFree=4182980/4192956
[pid=20416] ppid=20414 vsize=12268 CPUtime=0
/proc/20416/stat : 20416 (pbclasp) D 20414 20416 19380 0 -1 4194304 351 0 0 0 0 0 0 0 18 0 1 0 179736181 12562432 317 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 227607804517 0 2147483391 4224 0 18446744072099781622 0 0 17 1 0 0
/proc/20416/statm: 3067 317 242 3 0 167 0

[startup+0.0104899 s]
/proc/loadavg: 0.91 0.98 0.99 3/64 20416
/proc/meminfo: memFree=1813672/2055920 swapFree=4182980/4192956
[pid=20416] ppid=20414 vsize=12532 CPUtime=0
/proc/20416/stat : 20416 (pbclasp) R 20414 20416 19380 0 -1 4194304 489 0 0 0 0 0 0 0 18 0 1 0 179736181 12832768 455 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 227607486875 0 0 4224 16384 0 0 0 17 1 0 0
/proc/20416/statm: 3133 458 317 3 0 233 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12532

[startup+0.10151 s]
/proc/loadavg: 0.91 0.98 0.99 3/64 20416
/proc/meminfo: memFree=1813672/2055920 swapFree=4182980/4192956
[pid=20416] ppid=20414 vsize=12928 CPUtime=0.05
/proc/20416/stat : 20416 (pbclasp) S 20414 20416 19380 0 -1 4194304 640 0 0 0 5 0 0 0 16 0 1 0 179736181 13238272 590 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 227616534626 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/20416/statm: 3232 590 324 3 0 332 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 12928

[startup+0.301547 s]
/proc/loadavg: 0.91 0.98 0.99 3/64 20416
/proc/meminfo: memFree=1813672/2055920 swapFree=4182980/4192956
[pid=20416] ppid=20414 vsize=12928 CPUtime=0.05
/proc/20416/stat : 20416 (pbclasp) S 20414 20416 19380 0 -1 4194304 640 0 0 0 5 0 0 0 16 0 1 0 179736181 13238272 590 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 227616534626 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/20416/statm: 3232 590 324 3 0 332 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 12928

[startup+0.701627 s]
/proc/loadavg: 0.91 0.98 0.99 3/64 20416
/proc/meminfo: memFree=1813672/2055920 swapFree=4182980/4192956
[pid=20416] ppid=20414 vsize=13192 CPUtime=0.39
/proc/20416/stat : 20416 (pbclasp) S 20414 20416 19380 0 -1 4194304 832 1592 0 0 6 0 32 1 16 0 1 0 179736181 13508608 654 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 227616538516 0 0 4230 16384 18446744071563356171 0 0 17 0 0 0
/proc/20416/statm: 3298 654 343 3 0 398 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 13192

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

Child status: 0
Real time (s): 0.783449
CPU time (s): 0.78088
CPU user time (s): 0.747886
CPU system time (s): 0.032994
CPU usage (%): 99.6721
Max. virtual memory (cumulated for all children) (KiB): 13192

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.747886
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= 4708
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= 126
involuntary context switches= 47

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node66 on Fri Apr 20 02:51:06 UTC 2007

IDJOB= 364152
IDBENCH= 2073
IDSOLVER= 158
FILE ID= node66/364152-1177037466

PBS_JOBID= 4640098

Free space on /tmp= 66408 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-bf0432-007.opb
COMMAND LINE= pbclasp instance-364152-1177037466.opb /tmp/evaluation/364152-1177037466/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node66/convwatcher-364152-1177037466 -o ROOT/results/node66/conversion-364152-1177037466 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/364152-1177037466/instance-364152-1177037466.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 814f1745fa20958d8b352781cfa0403e
MD5SUM BENCH=  093787cffe9173c370b11fb5e77a5812

RANDOM SEED= 662202987

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node66.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.281
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.281
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:       1814080 kB
Buffers:         36408 kB
Cached:         138640 kB
SwapCached:       3792 kB
Active:          45056 kB
Inactive:       141444 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1814080 kB
SwapTotal:     4192956 kB
SwapFree:      4182980 kB
Dirty:            1340 kB
Writeback:           0 kB
Mapped:          16372 kB
Slab:            41396 kB
Committed_AS:   958060 kB
PageTables:       1380 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= 66408 MiB

End job on node66 on Fri Apr 20 02:51:07 UTC 2007