Trace number 35760

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 9.78351 9.79347

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/
lp/data/normalized-mps-v2-20-10-nesm.opb
MD5SUM31474359e26932e1c53f8471ac3551eb
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 benchmark9.00463
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables60075
Total number of constraints2257
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 constraints2257
Minimum length of a constraint10
Maximum length of a constraint941
Number of terms in the objective function 8142
Biggest coefficient in the objective function 104857600000000000
Number of bits for the biggest coefficient in the objective function 57
Sum of the numbers in the objective function 5247199281280502271
Number of bits of the sum of numbers in the objective function 63
Biggest number in a constraint 1789569420335513600
Number of bits of the biggest number in a constraint 61
Biggest sum of numbers in a constraint 7218026776828457671
Number of bits of the biggest sum of numbers63
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...
5.88	c Converting 2721 PB-constraints to clauses...
5.91	c   -- Unit propagations: pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp  -- Detecting intervals from adjacent constraints: ######################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################
9.78	c   -- Clauses(.)/Splits(s): s
9.78	s UNSATISFIABLE
9.78	c _______________________________________________________________________________
9.78	c 
9.78	c restarts              : 0
9.78	c conflicts             : 0              (0 /sec)
9.78	c decisions             : 0              (0 /sec)
9.78	c propagations          : 0              (0 /sec)
9.78	c inspects              : 0              (0 /sec)
9.78	c CPU time              : 9.73052 s
9.78	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/node89/watcher-35760-1149309657 -o ROOT/results/node89/solver-35760-1149309657 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node89/35760-1149309657/instance-35760-1149309657.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.86 0.94 0.95 2/68 24549
/proc/meminfo: memFree=1543960/2055892 swapFree=4085360/4096564
[pid=24549] ppid=24547 vsize=1048 CPUtime=0
/proc/24549/stat : 24549 (minisat+) R 24547 24549 24503 0 -1 4194304 113 0 0 0 0 0 0 0 19 0 1 0 196604757 1073152 100 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 135007481 0 0 4096 16386 0 0 0 17 1 0 0
/proc/24549/statm: 295 102 67 215 0 77 0

Child status: 20
Real time (s): 9.79347
CPU time (s): 9.78351
CPU user time (s): 9.73052
CPU system time (s): 0.052991
CPU usage (%): 99.8983
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node89 on Sat Jun  3 04:40:57 UTC 2006


FILE ID= 35760-1149309657

PBS_JOBID= 307875

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-nesm.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node89/35760-1149309657/instance-35760-1149309657.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node89/watcher-35760-1149309657 -o ROOT/results/node89/solver-35760-1149309657 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node89/35760-1149309657/instance-35760-1149309657.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  31474359e26932e1c53f8471ac3551eb

RANDOM SEED= 156024993


/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.265
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	: 6006.16
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.265
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	: 5999.43
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1544168 kB
Buffers:         40232 kB
Cached:         397644 kB
SwapCached:       2560 kB
Active:         120000 kB
Inactive:       326708 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1544168 kB
SwapTotal:     4096564 kB
SwapFree:      4085360 kB
Dirty:             320 kB
Writeback:           0 kB
Mapped:          16536 kB
Slab:            51568 kB
Committed_AS:   320708 kB
PageTables:       1300 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node89 on Sat Jun  3 04:41:07 UTC 2006