Trace number 33570

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
PB-smodels 1.28SAT 0.442932 0.357936

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900547416.opb
MD5SUMb3be50396cebacd2fb0dd8b51b7d346c
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.197969
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables231
Total number of constraints2707
Number of constraints which are clauses2684
Number of constraints which are cardinality constraints (but not clauses)22
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint110
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 25
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 747
Number of bits of the biggest sum of numbers10
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 Running pbsmodels-v1.28
0.35	s SATISFIABLE
0.35	v x3 x16 x23 x42 x51 x59 x74 x79 x98 x105 x121 x162 x193 x224 x185 x145 x217 x208 x158 x129 x140 x181 -x1 -x12 -x2 -x13 -x14 -x4 -x15
0.35	v -x5 -x6 -x17 -x7 -x18 -x8 -x19 -x9 -x20 -x10 -x21 -x11 -x22 -x24 -x25 -x26 -x27 -x28 -x29 -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37
0.35	v -x38 -x39 -x40 -x41 -x43 -x44 -x45 -x46 -x47 -x48 -x49 -x50 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x60 -x61 -x62 -x63 -x64 -x65 -x66
0.35	v -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x75 -x76 -x77 -x78 -x80 -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94
0.35	v -x95 -x96 -x97 -x99 -x100 -x101 -x102 -x103 -x104 -x106 -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117
0.35	v -x118 -x119 -x120 -x132 -x142 -x152 -x172 -x182 -x192 -x202 -x212 -x222 -x122 -x143 -x153 -x163 -x173 -x183 -x203 -x213 -x223
0.35	v -x123 -x133 -x154 -x164 -x174 -x184 -x194 -x204 -x214 -x124 -x134 -x144 -x165 -x175 -x195 -x205 -x215 -x225 -x125 -x135 -x155
0.35	v -x176 -x186 -x196 -x206 -x216 -x226 -x126 -x136 -x146 -x156 -x166 -x187 -x197 -x207 -x227 -x127 -x137 -x147 -x157 -x167 -x177
0.35	v -x198 -x218 -x228 -x128 -x138 -x148 -x168 -x178 -x188 -x209 -x219 -x229 -x139 -x149 -x159 -x169 -x179 -x189 -x199 -x220 -x230
0.35	v -x130 -x150 -x160 -x170 -x180 -x190 -x200 -x210 -x231 -x131 -x141 -x151 -x161 -x171 -x191 -x201 -x211 -x221

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

runsolver version 3.0.1 (c) roussel@cril.univ-artois.fr

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node83/watcher-33570-1149620252 -o ROOT/results/node83/solver-33570-1149620252 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node83/33570-1149620252/instance-33570-1149620252.opb 641406602 ROOT/tmp/node83/33570-1149620252 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.71 0.39 0.15 2/67 31289
/proc/meminfo: memFree=1572064/2055888 swapFree=4085408/4096564
[pid=31289] ppid=31287 vsize=5360 CPUtime=0
/proc/31289/stat : 31289 (runpbsmodels) R 31287 31289 31243 0 -1 4194304 158 0 0 0 0 0 0 0 20 0 1 0 227664558 5488640 128 18446744073709551615 4194304 4889804 548682069168 18446744073709551615 242290720432 0 0 4096 0 0 0 0 17 1 0 0
/proc/31289/statm: 1341 140 113 169 0 51 0

Child status: 0
Real time (s): 0.357936
CPU time (s): 0.442932
CPU user time (s): 0.431934
CPU system time (s): 0.010998
CPU usage (%): 123.746
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node83 on Tue Jun  6 18:57:32 UTC 2006


FILE ID= 33570-1149620252

PBS_JOBID= 322389

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/tsp/normalized-t3002.11tsp11.1900547416.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node83/33570-1149620252/instance-33570-1149620252.opb 641406602  ROOT/tmp/node83/33570-1149620252
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node83/watcher-33570-1149620252 -o ROOT/results/node83/solver-33570-1149620252 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node83/33570-1149620252/instance-33570-1149620252.opb 641406602  ROOT/tmp/node83/33570-1149620252

MD5SUM SOLVER= f639f6b7f53e3afd14340f75c0e271ee 82c14a26114306e436bf36ef1d1c85a0 c893ceb51a2aaa4ab2f96d97b043cdf0 8c810dcfce02286b111d075d14837741 79b233270d136fcdcf9d8f80d20efef0
MD5SUM BENCH=  b3be50396cebacd2fb0dd8b51b7d346c

RANDOM SEED= 641406602


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


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1572336 kB
Buffers:         34116 kB
Cached:         379408 kB
SwapCached:       2364 kB
Active:          81996 kB
Inactive:       340200 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1572336 kB
SwapTotal:     4096564 kB
SwapFree:      4085408 kB
Dirty:             164 kB
Writeback:           0 kB
Mapped:          16888 kB
Slab:            48052 kB
Committed_AS:   481960 kB
PageTables:       1284 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node83 on Tue Jun  6 18:57:32 UTC 2006