Trace number 41123

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 NameAnswerCPU timeWall clock time
PBS 4.1LSAT 1.9887 1.99419

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga13_13_sat_pb.cnf.cr.opb
MD5SUMbf7e21954a6ae09c036e6d4bdde8af91
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.003998
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables254
Total number of constraints208
Number of constraints which are clauses182
Number of constraints which are cardinality constraints (but not clauses)26
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint6
Maximum length of a constraint13
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 14
Number of bits of the biggest sum of numbers4
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 PBS v4 by Bashar Al-Rawi & Fadi Aloul
0.00	c Solving ROOT/tmp/node36/41123-1149234492/instance-41123-1149234492.opb ......
1.99	c done parsing opb.
1.99	s SATISFIABLE
1.99	c Total Run Time					1.9817
1.99	v -x1 -x10 -x100 -x101 -x102 -x103 -x104 -x105 -x106 -x107 -x108 -x109 -x11 -x110 -x111 -x112 -x113 -x114 x115 -x116 -x117 -x118
1.99	v x119 -x12 -x120 -x121 -x122 -x123 -x124 -x125 -x126 -x127 -x128 -x129 -x13 -x130 -x131 -x132 -x133 -x134 -x135 -x136 -x137
1.99	v -x138 -x139 -x14 -x140 -x141 -x142 x143 -x144 -x145 -x146 -x147 -x148 -x149 -x15 -x150 -x151 -x152 -x153 -x154 x155 -x156
1.99	v -x157 -x158 -x159 -x16 -x160 -x161 -x162 -x163 -x164 -x165 x166 -x167 -x168 -x169 x17 -x170 -x171 -x172 -x173 -x174 x175 -x176
1.99	v -x177 x178 -x179 -x18 -x180 -x181 -x182 -x183 -x184 -x185 x186 -x187 -x188 x189 -x19 -x190 -x191 -x192 -x193 x194 -x195 -x196
1.99	v -x197 -x198 -x199 -x2 -x20 -x200 -x201 -x202 x203 -x204 -x205 x206 -x207 -x208 -x209 -x21 -x210 -x211 -x212 -x213 -x214 -x215
1.99	v -x216 -x217 -x218 x219 -x22 -x220 -x221 -x222 -x223 x224 -x225 -x226 -x227 x228 -x229 -x23 -x230 -x231 -x232 -x233 -x234 -x235
1.99	v x236 -x237 -x238 -x239 -x24 -x240 -x241 -x242 -x243 -x244 -x245 x246 -x247 -x248 -x249 -x25 -x250 x251 -x252 -x253 -x254 -x26
1.99	v x27 -x28 -x29 -x3 -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x4 -x40 -x41 -x42 -x43 -x44 -x45 x46 -x47 -x48 -x49 x5 -x50
1.99	v -x51 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x6 -x60 x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x7 -x70 -x71 -x72 x73 -x74 -x75
1.99	v -x76 -x77 -x78 -x79 -x8 -x80 x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x9 -x90 -x91 -x92 -x93 -x94 -x95 -x96 x97 -x98 -x99

Verifier Data (download as text)

OK	0

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/node36/watcher-41123-1149234492 -o ROOT/results/node36/solver-41123-1149234492 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node36/41123-1149234492/instance-41123-1149234492.opb 730623014 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.73 0.91 0.89 2/64 21414
/proc/meminfo: memFree=1357208/2055920 swapFree=4181460/4192956
[pid=21414] ppid=21412 vsize=1400 CPUtime=0
/proc/21414/stat : 21414 (PBS4L) R 21412 21414 21369 0 -1 4194304 135 0 0 0 0 0 0 0 18 0 1 0 189115293 1433600 119 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 135084712 0 0 4096 0 0 0 0 17 1 0 0
/proc/21414/statm: 350 124 97 232 0 115 0

Child status: 0
Real time (s): 1.99419
CPU time (s): 1.9887
CPU user time (s): 1.9707
CPU system time (s): 0.017997
CPU usage (%): 99.7247
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node36 on Fri Jun  2 07:48:12 UTC 2006


FILE ID= 41123-1149234492

PBS_JOBID= 296754

BENCH NAME= ROOT/tmp/node36/41123-1149234492/instance-41123-1149234492.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node36/41123-1149234492/instance-41123-1149234492.opb 730623014
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node36/watcher-41123-1149234492 -o ROOT/results/node36/solver-41123-1149234492 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node36/41123-1149234492/instance-41123-1149234492.opb 730623014

MD5SUM SOLVER= ab46593c31a6a47b9d9920387a00d332
MD5SUM BENCH=  bf7e21954a6ae09c036e6d4bdde8af91

RANDOM SEED= 730623014


/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.284
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.284
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:       1357416 kB
Buffers:         40400 kB
Cached:         581764 kB
SwapCached:       3504 kB
Active:         194336 kB
Inactive:       436824 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1357416 kB
SwapTotal:     4192956 kB
SwapFree:      4181460 kB
Dirty:             280 kB
Writeback:           0 kB
Mapped:          14924 kB
Slab:            53432 kB
Committed_AS:   187596 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node36 on Fri Jun  2 07:48:14 UTC 2006