Trace number 84694

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
glpPB 0.2SAT 43.2714 43.2918

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900554154.opb
MD5SUM25407f9a05a0681e4105dea00c619664
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.077987
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 655
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 glpPB 0.2 (July 2006)
0.00	c An Application of GLPK 4.10 for PB Constraints
0.00	c Done @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
43.28	c starting to Solve
43.28	c total time = 43.26
43.28	c quality of integer solution is H
43.28	s SATISFIABLE
43.28	v x1 -x12 -x2 x13 -x3 -x14 -x4 -x15 -x5 -x16 -x6 -x17 -x7 -x18 -x8 -x19 -x9 -x20 -x10 -x21 -x11 -x22 -x23 -x24 -x25 x26 -x27 -x28 -x29
43.28	v -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 x42 -x43 -x44 -x45 -x46 -x47 -x48 -x49 -x50 -x51 -x52 -x53 -x54 x55
43.28	v -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80 -x81
43.28	v -x82 x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105 -x106
43.28	v x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 x115 -x116 -x117 -x118 -x119 -x120 -x121 -x132 -x142 -x152 x162 -x172 -x182
43.28	v -x192 -x202 -x212 -x222 x122 -x143 -x153 -x163 -x173 -x183 -x193 -x203 -x213 -x223 -x123 -x133 -x154 -x164 x174 -x184 -x194
43.28	v -x204 -x214 -x224 -x124 x134 -x144 -x165 -x175 -x185 -x195 -x205 -x215 -x225 -x125 -x135 -x145 -x155 -x176 -x186 x196 -x206
43.28	v -x216 -x226 -x126 -x136 -x146 -x156 -x166 x187 -x197 -x207 -x217 -x227 -x127 -x137 -x147 -x157 -x167 -x177 -x198 -x208 x218
43.28	v -x228 -x128 -x138 x148 -x158 -x168 -x178 -x188 -x209 -x219 -x229 -x129 -x139 -x149 x159 -x169 -x179 -x189 -x199 -x220 -x230
43.28	v -x130 -x140 -x150 -x160 -x170 -x180 -x190 -x200 -x210 x231 -x131 -x141 -x151 -x161 -x171 -x181 -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.3 (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/node2/watcher-84694-1154158632 -o ROOT/results/node2/solver-84694-1154158632 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node2/84694-1154158632/instance-84694-1154158632.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.99 0.97 0.82 3/64 5115
/proc/meminfo: memFree=1239200/2055920 swapFree=4182688/4192956
[pid=5115] ppid=5113 vsize=2420 CPUtime=0
/proc/5115/stat : 5115 (glpPBv3) R 5113 5115 5066 0 -1 0 69 0 0 0 0 0 0 0 18 0 1 0 162724796 2478080 52 18446744073709551615 134512640 134678228 4294956688 18446744073709551615 10518468 0 0 4096 0 0 0 0 17 1 0 0
/proc/5115/statm: 606 61 49 40 0 11 0

[startup+10.002 s]
/proc/loadavg: 0.99 0.97 0.83 2/64 5115
/proc/meminfo: memFree=1235936/2055920 swapFree=4182688/4192956
[pid=5115] ppid=5113 vsize=5632 CPUtime=9.99
/proc/5115/stat : 5115 (glpPBv3) R 5113 5115 5066 0 -1 0 1388 0 0 0 997 2 0 0 25 0 1 0 162724796 5767168 1034 18446744073709551615 134512640 134678228 4294956688 18446744073709551615 134643580 0 0 4096 0 0 0 0 17 1 0 0
/proc/5115/statm: 1408 1034 227 40 0 825 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 5632

[startup+20.0078 s]
/proc/loadavg: 0.99 0.97 0.83 2/64 5115
/proc/meminfo: memFree=1235936/2055920 swapFree=4182688/4192956
[pid=5115] ppid=5113 vsize=5632 CPUtime=19.99
/proc/5115/stat : 5115 (glpPBv3) R 5113 5115 5066 0 -1 0 1873 0 0 0 1995 4 0 0 25 0 1 0 162724796 5767168 1034 18446744073709551615 134512640 134678228 4294956688 18446744073709551615 134541542 0 0 4096 0 0 0 0 17 1 0 0
/proc/5115/statm: 1408 1034 227 40 0 825 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 5632

[startup+30.0136 s]
/proc/loadavg: 0.99 0.97 0.83 2/64 5115
/proc/meminfo: memFree=1235936/2055920 swapFree=4182688/4192956
[pid=5115] ppid=5113 vsize=5632 CPUtime=29.99
/proc/5115/stat : 5115 (glpPBv3) R 5113 5115 5066 0 -1 0 2313 0 0 0 2993 6 0 0 25 0 1 0 162724796 5767168 1034 18446744073709551615 134512640 134678228 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/5115/statm: 1408 1034 227 40 0 825 0
Current children cumulated CPU time (s) 29.99
Current children cumulated vsize (Kb) 5632

[startup+40.0195 s]
/proc/loadavg: 0.99 0.97 0.83 2/64 5115
/proc/meminfo: memFree=1235872/2055920 swapFree=4182688/4192956
[pid=5115] ppid=5113 vsize=5632 CPUtime=40
/proc/5115/stat : 5115 (glpPBv3) R 5113 5115 5066 0 -1 0 2813 0 0 0 3991 9 0 0 25 0 1 0 162724796 5767168 1034 18446744073709551615 134512640 134678228 4294956688 18446744073709551615 134544666 0 0 4096 0 0 0 0 17 1 0 0
/proc/5115/statm: 1408 1034 227 40 0 825 0
Current children cumulated CPU time (s) 40
Current children cumulated vsize (Kb) 5632

Child status: 10
Real time (s): 43.2918
CPU time (s): 43.2714
CPU user time (s): 43.1714
CPU system time (s): 0.099984
CPU usage (%): 99.9529
Max. virtual memory (cumulated for all children) (Kb): 5632
The end

Launcher Data (download as text)

Begin job on node2 on Sat Jul 29 07:37:12 UTC 2006


FILE ID= 84694-1154158632

PBS_JOBID= 892468

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/tsp/normalized-t3002.11tsp11.1900554154.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node2/84694-1154158632/instance-84694-1154158632.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-84694-1154158632 -o ROOT/results/node2/solver-84694-1154158632 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node2/84694-1154158632/instance-84694-1154158632.opb

MD5SUM SOLVER= 29ce95346658d7502ba983059bfb8cff
MD5SUM BENCH=  25407f9a05a0681e4105dea00c619664

RANDOM SEED= 73460119

TIMEOUT= 1800 seconds


/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.276
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.276
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:       1239472 kB
Buffers:         44472 kB
Cached:         694028 kB
SwapCached:       3992 kB
Active:         125752 kB
Inactive:       621668 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1239472 kB
SwapTotal:     4192956 kB
SwapFree:      4182688 kB
Dirty:             196 kB
Writeback:           0 kB
Mapped:          14528 kB
Slab:            55024 kB
Committed_AS:   737888 kB
PageTables:       1492 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node2 on Sat Jul 29 07:37:56 UTC 2006