Trace number 39602

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
bsolo 2006/05SAT 15.2377 15.2591

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900574974.opb
MD5SUM78c4eb026aae2b7f6add2badfbe0cd2c
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.128979
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 663
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 Time Limit set via PBTIMEOUT to 1800
0.02	c INFO: OSL Context initialized.
0.07	c Initial problem consists of 231 variables and 2707 constraints.
0.08	c Using non-optimization problem switches.
0.08	c No problem reductions applied in OPT. instance.
0.08	c	preprocess terminated. Elapsed time: 0.07
0.08	c After prepocess the problem consists of 231 variables and 2586 constraints.
0.12	c Restart #1 #Var: 231 LB: 0 @ 0.112
0.24	c Restart #2 #Var: 231 LB: 0 @ 0.232
0.41	c Restart #3 #Var: 231 LB: 0 @ 0.397
0.62	c Restart #4 #Var: 231 LB: 0 @ 0.612
0.82	c Restart #5 #Var: 231 LB: 0 @ 0.811
1.05	c Restart #6 #Var: 231 LB: 0 @ 1.039
1.32	c Restart #7 #Var: 231 LB: 0 @ 1.306
1.66	c Restart #8 #Var: 231 LB: 0 @ 1.648
2.05	c Restart #9 #Var: 231 LB: 0 @ 2.039
2.87	c Restart #10 #Var: 231 LB: 0 @ 2.863
3.47	c Restart #11 #Var: 231 LB: 0 @ 3.461
4.24	c Restart #12 #Var: 231 LB: 0 @ 4.231
5.07	c Restart #13 #Var: 231 LB: 0 @ 5.056
5.88	c Restart #14 #Var: 231 LB: 0 @ 5.872
6.84	c Restart #15 #Var: 231 LB: 0 @ 6.827
8.62	c Restart #16 #Var: 231 LB: 0 @ 8.605
9.84	c Restart #17 #Var: 231 LB: 0 @ 9.824
11.20	c Restart #18 #Var: 231 LB: 0 @ 11.178
12.84	c Restart #19 #Var: 231 LB: 0 @ 12.822
14.69	c Restart #20 #Var: 231 LB: 0 @ 14.668
15.25	c Sol. found (all assignments made)...
15.25	o 0
15.25	c NEW SOLUTION FOUND: 0 @ 15.229
15.25	s SATISFIABLE
15.25	c Cost: 0
15.25	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
15.25	v x29 -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
15.25	v -x55 -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
15.25	v -x81 x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 x100 -x101 -x102 -x103 -x104 -x105
15.25	v -x106 -x107 -x108 -x109 -x110 -x111 -x112 x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 x132 -x142 -x152 -x162 -x172
15.25	v -x182 -x192 -x202 -x212 -x222 -x122 -x143 -x153 x163 -x173 -x183 -x193 -x203 -x213 -x223 x123 -x133 -x154 -x164 -x174 -x184
15.25	v -x194 -x204 -x214 -x224 -x124 -x134 -x144 -x165 -x175 -x185 -x195 x205 -x215 -x225 -x125 -x135 -x145 -x155 -x176 -x186 -x196
15.25	v -x206 x216 -x226 -x126 -x136 -x146 -x156 -x166 x187 -x197 -x207 -x217 -x227 -x127 -x137 -x147 -x157 -x167 -x177 -x198 -x208
15.25	v -x218 x228 -x128 -x138 x148 -x158 -x168 -x178 -x188 -x209 -x219 -x229 -x129 -x139 -x149 -x159 -x169 x179 -x189 -x199 -x220
15.25	v -x230 -x130 -x140 -x150 x160 -x170 -x180 -x190 -x200 -x210 -x231 -x131 -x141 -x151 -x161 -x171 -x181 -x191 x201 -x211 -x221
15.25	c Exit Code: 10
15.25	c Total time: 15.231 s

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/node84/watcher-39602-1149223036 -o ROOT/results/node84/solver-39602-1149223036 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node84/39602-1149223036/instance-39602-1149223036.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.60 0.89 0.91 4/67 10382
/proc/meminfo: memFree=1732000/2055892 swapFree=4085292/4096564
[pid=10382] ppid=10380 vsize=436 CPUtime=0
/proc/10382/stat : 10382 (bsolo) D 10380 10382 10337 0 -1 0 37 0 0 0 0 0 0 0 20 0 1 0 187942908 446464 23 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 8106932 0 2147483391 4096 0 18446744072099917094 0 0 17 1 0 0
/proc/10382/statm: 109 23 18 55 0 18 0

[startup+10.0028 s]
/proc/loadavg: 0.66 0.89 0.91 2/67 10382
/proc/meminfo: memFree=1710880/2055892 swapFree=4085292/4096564
[pid=10382] ppid=10380 vsize=25608 CPUtime=9.98
/proc/10382/stat : 10382 (bsolo) R 10380 10382 10337 0 -1 0 5656 0 0 0 993 5 0 0 25 0 1 0 187942908 26222592 5572 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134718518 0 0 4096 16384 0 0 0 17 0 0 0
/proc/10382/statm: 6402 5572 293 55 0 5293 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 25608

Child status: 10
Real time (s): 15.2591
CPU time (s): 15.2377
CPU user time (s): 15.1607
CPU system time (s): 0.076988
CPU usage (%): 99.8596
Max. virtual memory (cumulated for all children) (Kb): 25608

Launcher Data (download as text)

Begin job on node84 on Fri Jun  2 04:37:16 UTC 2006


FILE ID= 39602-1149223036

PBS_JOBID= 295578

BENCH NAME= ROOT/tmp/node84/39602-1149223036/instance-39602-1149223036.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node84/39602-1149223036/instance-39602-1149223036.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node84/watcher-39602-1149223036 -o ROOT/results/node84/solver-39602-1149223036 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node84/39602-1149223036/instance-39602-1149223036.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  78c4eb026aae2b7f6add2badfbe0cd2c

RANDOM SEED= 553825938


/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.231
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.15
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.231
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:       1732208 kB
Buffers:         23412 kB
Cached:         230292 kB
SwapCached:       2520 kB
Active:          91900 kB
Inactive:       170480 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1732208 kB
SwapTotal:     4096564 kB
SwapFree:      4085292 kB
Dirty:             272 kB
Writeback:           0 kB
Mapped:          16412 kB
Slab:            47996 kB
Committed_AS:   257372 kB
PageTables:       1272 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node84 on Fri Jun  2 04:37:31 UTC 2006