Trace number 35820

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
minisat+ 1.14UNSAT 14.5448 14.5568

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/
lp/data/normalized-mps-v2-20-10-fffff800.opb
MD5SUM0f197dc54398ded0c8eff8292928b1a0
Bench CategoryOPT-BIGINT (optimisation, big 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 benchmark4.00339
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables25620
Total number of constraints524
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 constraints524
Minimum length of a constraint30
Maximum length of a constraint7530
Number of terms in the objective function 240
Biggest coefficient in the objective function 536870912
Number of bits for the biggest coefficient in the objective function 30
Sum of the numbers in the objective function 8589934584
Number of bits of the sum of numbers in the objective function 33
Biggest number in a constraint 16106127360000000000
Number of bits of the biggest number in a constraint 64
Biggest sum of numbers in a constraint 392918753328864668366
Number of bits of the biggest sum of numbers69
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 Parsing PB file...
3.63	c Converting 810 PB-constraints to clauses...
3.64	c   -- Unit propagations: ppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp  -- Detecting intervals from adjacent constraints: ############################################################################################################################################################################################################################################################=##################################################
14.55	c   -- Clauses(.)/Splits(s): s
14.55	s UNSATISFIABLE
14.55	c _______________________________________________________________________________
14.55	c 
14.55	c restarts              : 0
14.55	c conflicts             : 0              (0 /sec)
14.55	c decisions             : 0              (0 /sec)
14.55	c propagations          : 0              (0 /sec)
14.55	c inspects              : 0              (0 /sec)
14.55	c CPU time              : 14.5098 s
14.55	c _______________________________________________________________________________

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/node19/watcher-35820-1149312746 -o ROOT/results/node19/solver-35820-1149312746 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node19/35820-1149312746/instance-35820-1149312746.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.78 0.96 0.98 2/64 8020
/proc/meminfo: memFree=1568368/2055920 swapFree=4181404/4192956
[pid=8020] ppid=8018 vsize=1048 CPUtime=0
/proc/8020/stat : 8020 (minisat+) R 8018 8020 7974 0 -1 4194304 105 0 0 0 0 0 0 0 18 0 1 0 196937685 1073152 90 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 135007481 0 0 4096 16386 0 0 0 17 1 0 0
/proc/8020/statm: 262 90 67 215 0 44 0

[startup+10.0021 s]
/proc/loadavg: 0.81 0.96 0.98 2/64 8020
/proc/meminfo: memFree=1549128/2055920 swapFree=4181404/4192956
[pid=8020] ppid=8018 vsize=21060 CPUtime=9.98
/proc/8020/stat : 8020 (minisat+) R 8018 8020 7974 0 -1 4194304 6302 0 0 0 996 2 0 0 25 0 1 0 196937685 21565440 4895 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 135005777 0 0 4096 16386 0 0 0 17 1 0 0
/proc/8020/statm: 5265 4895 83 215 0 5047 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 21060

Child status: 20
Real time (s): 14.5568
CPU time (s): 14.5448
CPU user time (s): 14.5108
CPU system time (s): 0.033994
CPU usage (%): 99.9173
Max. virtual memory (cumulated for all children) (Kb): 21060

Launcher Data (download as text)

Begin job on node19 on Sat Jun  3 05:32:27 UTC 2006


FILE ID= 35820-1149312746

PBS_JOBID= 308112

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/lp/data/normalized-mps-v2-20-10-fffff800.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node19/35820-1149312746/instance-35820-1149312746.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node19/watcher-35820-1149312746 -o ROOT/results/node19/solver-35820-1149312746 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node19/35820-1149312746/instance-35820-1149312746.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  0f197dc54398ded0c8eff8292928b1a0

RANDOM SEED= 158006527


/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.236
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.236
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:       1568640 kB
Buffers:         25044 kB
Cached:         390900 kB
SwapCached:       3208 kB
Active:          66528 kB
Inactive:       358156 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1568640 kB
SwapTotal:     4192956 kB
SwapFree:      4181404 kB
Dirty:             344 kB
Writeback:           0 kB
Mapped:          14732 kB
Slab:            48640 kB
Committed_AS:   363996 kB
PageTables:       1488 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node19 on Sat Jun  3 05:32:41 UTC 2006