Trace number 35512

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.14OPT100 0.035993 0.0403999

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-100-1_6-yes1-2.opb
MD5SUM7ec59a0b091bf2338a9ae3083dc2bac0
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.004999
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 constraints260
Number of constraints which are clauses259
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	c Parsing PB file...
0.01	c Converting 260 PB-constraints to clauses...
0.01	c   -- Unit propagations: (none)
0.01	c   -- Detecting intervals from adjacent constraints: (none)
0.01	c   -- Clauses(.)/Splits(s): ....................................................................................................................................................................................................................................................................
0.01	c ==================================[MINISAT+]==================================
0.01	c | Conflicts | Original         | Learnt                           | Progress |
0.01	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.01	c ==============================================================================
0.01	c |         0 |     260      679 |      86       0        0     nan |  0.000 % |
0.01	c ==============================================================================
0.01	c Found solution: 100
0.01	o 100
0.01	c ---[   0]---> Sorter-cost: 5006     Base:
0.03	c ==================================[MINISAT+]==================================
0.03	c | Conflicts | Original         | Learnt                           | Progress |
0.03	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.03	c ==============================================================================
0.03	c |        22 |    5997    14098 |    1999      17       55     3.2 |  0.000 % |
0.03	c ==============================================================================
0.03	c Optimal solution: 100
0.03	s OPTIMUM FOUND
0.03	v x1 -x2 -x3 x4 x5 -x6 -x7 x8 x9 -x10 x11 -x12 -x13 x14 x15 -x16 -x17 x18 -x19 x20 x21 -x22 x23 -x24 x25 -x26 x27 -x28 x29 -x30 -x31 x32
0.03	v -x33 x34 x35 -x36 x37 -x38 -x39 x40 -x41 x42 -x43 x44 x45 -x46 x47 -x48 x49 -x50 x51 -x52 -x53 x54 -x55 x56 -x57 x58 -x59 x60 -x61
0.03	v x62 x63 -x64 -x65 x66 -x67 x68 x69 -x70 x71 -x72 -x73 x74 x75 -x76 -x77 x78 x79 -x80 -x81 x82 x83 -x84 x85 -x86 -x87 x88 x89 -x90
0.03	v -x91 x92 x93 -x94 -x95 x96 -x97 x98 x99 -x100 x101 -x102 -x103 x104 -x105 x106 x107 -x108 -x109 x110 -x111 x112 x113 -x114 x115
0.03	v -x116 x117 -x118 -x119 x120 -x121 x122 -x123 x124 -x125 x126 -x127 x128 x129 -x130 -x131 x132 -x133 x134 x135 -x136 x137 -x138
0.03	v -x139 x140 x141 -x142 -x143 x144 x145 -x146 x147 -x148 -x149 x150 -x151 x152 -x153 x154 x155 -x156 x157 -x158 -x159 x160 x161
0.03	v -x162 x163 -x164 x165 -x166 x167 -x168 -x169 x170 -x171 x172 -x173 x174 x175 -x176 x177 -x178 x179 -x180 -x181 x182 -x183 x184
0.03	v x185 -x186 -x187 x188 x189 -x190 -x191 x192 -x193 x194 -x195 x196 -x197 x198 x199 -x200
0.03	c _______________________________________________________________________________
0.03	c 
0.03	c restarts              : 2
0.03	c conflicts             : 36             (1059 /sec)
0.03	c decisions             : 163            (4795 /sec)
0.03	c propagations          : 0              (0 /sec)
0.03	c inspects              : 0              (0 /sec)
0.03	c CPU time              : 0.033994 s
0.03	c _______________________________________________________________________________

Verifier Data (download as text)

OK	100

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.92 0.98 0.99 2/64 32135
/proc/meminfo: memFree=1825456/2055920 swapFree=4181320/4192956
[pid=32135] ppid=32133 vsize=1048 CPUtime=0
/proc/32135/stat : 32135 (minisat+) R 32133 32135 32089 0 -1 4194304 113 0 0 0 0 0 0 0 19 0 1 0 207662490 1073152 98 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 135031278 0 0 4096 16386 0 0 0 17 1 0 0
/proc/32135/statm: 262 98 74 215 0 44 0

Child status: 30
Real time (s): 0.0403999
CPU time (s): 0.035993
CPU user time (s): 0.033994
CPU system time (s): 0.001999
CPU usage (%): 89.0918
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node29 on Sun Jun  4 11:19:49 UTC 2006


FILE ID= 35512-1149419989

PBS_JOBID= 315704

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-100-1_6-yes1-2.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node29/35512-1149419989/instance-35512-1149419989.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node29/watcher-35512-1149419989 -o ROOT/results/node29/solver-35512-1149419989 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node29/35512-1149419989/instance-35512-1149419989.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  7ec59a0b091bf2338a9ae3083dc2bac0

RANDOM SEED= 477181854


/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.259
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.259
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:       1825664 kB
Buffers:         19276 kB
Cached:         145888 kB
SwapCached:       3068 kB
Active:          46936 kB
Inactive:       126604 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1825664 kB
SwapTotal:     4192956 kB
SwapFree:      4181320 kB
Dirty:             308 kB
Writeback:           0 kB
Mapped:          14492 kB
Slab:            42652 kB
Committed_AS:   418096 kB
PageTables:       1504 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node29 on Sun Jun  4 11:19:49 UTC 2006