Trace number 36603

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
Pueblo 1.4UNSAT 12.6631 12.6702

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/reduced/mps-v2-20-10/MIPLIB/
miplib2003/normalized-reduced-mps-v2-20-10-a1c1s1.opb
MD5SUM8e26f63addeab9c605a48fae9909490e
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 benchmark11.2703
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables107520
Total number of constraints3312
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints3312
Minimum length of a constraint50
Maximum length of a constraint820
Number of terms in the objective function 41280
Biggest coefficient in the objective function 2704
Number of bits for the biggest coefficient in the objective function 12
Sum of the numbers in the objective function 560432
Number of bits of the sum of numbers in the objective function 20
Biggest number in a constraint 261600
Number of bits of the biggest number in a constraint 18
Biggest sum of numbers in a constraint 560432
Number of bits of the biggest sum of numbers20
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	c Pueblo version 1.4 (September 2005)
0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
3.93	c starting to Solve
3.93	c #variables read: 107520 - #constraints read: 4561
12.66	c total time              : 12.65 s
12.66	s UNSATISFIABLE

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node69/watcher-36603-1149363271 -o ROOT/results/node69/solver-36603-1149363271 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node69/36603-1149363271/instance-36603-1149363271.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.98 0.99 3/64 26259
/proc/meminfo: memFree=1699644/2055920 swapFree=4182216/4192956
[pid=26259] ppid=26257 vsize=2572 CPUtime=0
/proc/26259/stat : 26259 (Pueblo) R 26257 26259 26213 0 -1 4194304 260 0 0 0 0 0 0 0 19 0 1 0 201997093 2633728 231 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 12418775 0 0 4096 0 0 0 0 17 1 0 0
/proc/26259/statm: 643 231 193 16 0 84 0

[startup+10.0023 s]
/proc/loadavg: 0.93 0.98 0.99 2/64 26259
/proc/meminfo: memFree=1653332/2055920 swapFree=4182216/4192956
[pid=26259] ppid=26257 vsize=51184 CPUtime=9.99
/proc/26259/stat : 26259 (Pueblo) R 26257 26259 26213 0 -1 4194304 495498 0 0 0 859 140 0 0 25 0 1 0 201997093 52412416 11758 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 134527956 0 0 4096 0 0 0 0 17 1 0 0
/proc/26259/statm: 12796 11758 206 16 0 12237 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 51184

Child status: 20
Real time (s): 12.6702
CPU time (s): 12.6631
CPU user time (s): 11.2513
CPU system time (s): 1.41179
CPU usage (%): 99.9436
Max. virtual memory (cumulated for all children) (Kb): 51184

Launcher Data (download as text)

Begin job on node69 on Sat Jun  3 19:34:31 UTC 2006


FILE ID= 36603-1149363271

PBS_JOBID= 311641

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/reduced/mps-v2-20-10/MIPLIB/miplib2003/normalized-reduced-mps-v2-20-10-a1c1s1.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node69/36603-1149363271/instance-36603-1149363271.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node69/watcher-36603-1149363271 -o ROOT/results/node69/solver-36603-1149363271 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node69/36603-1149363271/instance-36603-1149363271.opb

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  8e26f63addeab9c605a48fae9909490e

RANDOM SEED= 1305063


/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.232
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.232
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:       1699852 kB
Buffers:         32524 kB
Cached:         253396 kB
SwapCached:       2468 kB
Active:         117244 kB
Inactive:       177376 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1699852 kB
SwapTotal:     4192956 kB
SwapFree:      4182216 kB
Dirty:             300 kB
Writeback:           0 kB
Mapped:          15444 kB
Slab:            47444 kB
Committed_AS:   380424 kB
PageTables:       1496 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node69 on Sat Jun  3 19:34:44 UTC 2006