Trace number 39582

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 22.2426 22.2708

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900554067.opb
MD5SUMe4fb42fad6e5e99b3f9cfb09951614f4
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.110982
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 609
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.063
0.08	c After prepocess the problem consists of 231 variables and 2586 constraints.
0.12	c Restart #1 #Var: 231 LB: 0 @ 0.102
0.23	c Restart #2 #Var: 231 LB: 0 @ 0.218
0.37	c Restart #3 #Var: 231 LB: 0 @ 0.351
0.55	c Restart #4 #Var: 231 LB: 0 @ 0.532
0.80	c Restart #5 #Var: 231 LB: 0 @ 0.781
1.02	c Restart #6 #Var: 231 LB: 0 @ 1.005
1.30	c Restart #7 #Var: 231 LB: 0 @ 1.285
1.71	c Restart #8 #Var: 231 LB: 0 @ 1.692
2.12	c Restart #9 #Var: 231 LB: 0 @ 2.101
2.75	c Restart #10 #Var: 231 LB: 0 @ 2.732
3.32	c Restart #11 #Var: 231 LB: 0 @ 3.306
4.02	c Restart #12 #Var: 231 LB: 0 @ 4
4.72	c Restart #13 #Var: 231 LB: 0 @ 4.703
5.53	c Restart #14 #Var: 231 LB: 0 @ 5.517
6.46	c Restart #15 #Var: 231 LB: 0 @ 6.44
7.54	c Restart #16 #Var: 231 LB: 0 @ 7.524
8.96	c Restart #17 #Var: 231 LB: 0 @ 8.946
10.78	c Restart #18 #Var: 231 LB: 0 @ 10.763
12.36	c Restart #19 #Var: 231 LB: 0 @ 12.337
13.92	c Restart #20 #Var: 231 LB: 0 @ 13.893
16.53	c Restart #21 #Var: 231 LB: 0 @ 16.504
18.98	c Restart #22 #Var: 231 LB: 0 @ 18.959
21.39	c Restart #23 #Var: 231 LB: 0 @ 21.366
22.26	c Sol. found (all assignments made)...
22.26	o 0
22.26	c NEW SOLUTION FOUND: 0 @ 22.232
22.26	s SATISFIABLE
22.26	c Cost: 0
22.26	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
22.26	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
22.26	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
22.26	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
22.26	v -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 x118 -x119 -x120 -x121 -x132 -x142 -x152 -x162 -x172 x182
22.26	v -x192 -x202 -x212 -x222 -x122 x143 -x153 -x163 -x173 -x183 -x193 -x203 -x213 -x223 x123 -x133 -x154 -x164 -x174 -x184 -x194
22.26	v -x204 -x214 -x224 -x124 -x134 -x144 -x165 -x175 -x185 -x195 x205 -x215 -x225 -x125 -x135 -x145 x155 -x176 -x186 -x196 -x206
22.26	v -x216 -x226 -x126 -x136 -x146 -x156 -x166 -x187 -x197 -x207 -x217 x227 -x127 -x137 -x147 -x157 -x167 x177 -x198 -x208 -x218
22.26	v -x228 -x128 x138 -x148 -x158 -x168 -x178 -x188 -x209 -x219 -x229 -x129 -x139 -x149 -x159 -x169 -x179 -x189 x199 -x220 -x230
22.26	v -x130 -x140 -x150 -x160 x170 -x180 -x190 -x200 -x210 -x231 -x131 -x141 -x151 -x161 -x171 -x181 -x191 -x201 -x211 x221
22.26	c Exit Code: 10
22.26	c Total time: 22.233 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/node11/watcher-39582-1149220900 -o ROOT/results/node11/solver-39582-1149220900 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node11/39582-1149220900/instance-39582-1149220900.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.88 0.95 0.91 3/64 20520
/proc/meminfo: memFree=1561672/2055920 swapFree=4181380/4192956
[pid=20520] ppid=20518 vsize=4664 CPUtime=0
/proc/20520/stat : 20520 (bsolo) R 20518 20520 20475 0 -1 0 155 0 0 0 0 0 0 0 19 0 1 0 187752535 4775936 135 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 7949588 0 0 4096 0 0 0 0 17 1 0 0
/proc/20520/statm: 1166 135 105 55 0 46 0

[startup+10.0025 s]
/proc/loadavg: 0.90 0.95 0.91 2/64 20520
/proc/meminfo: memFree=1539216/2055920 swapFree=4181380/4192956
[pid=20520] ppid=20518 vsize=26920 CPUtime=9.98
/proc/20520/stat : 20520 (bsolo) R 20518 20520 20475 0 -1 0 6000 0 0 0 992 6 0 0 25 0 1 0 187752535 27566080 5915 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20520/statm: 6730 5915 296 55 0 5622 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 26920

[startup+20.0087 s]
/proc/loadavg: 0.91 0.96 0.91 2/64 20520
/proc/meminfo: memFree=1525848/2055920 swapFree=4181380/4192956
[pid=20520] ppid=20518 vsize=40256 CPUtime=19.98
/proc/20520/stat : 20520 (bsolo) R 20518 20520 20475 0 -1 0 9331 0 0 0 1988 10 0 0 25 0 1 0 187752535 41222144 9246 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134533942 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20520/statm: 10064 9246 296 55 0 8956 0
Current children cumulated CPU time (s) 19.98
Current children cumulated vsize (Kb) 40256

Child status: 10
Real time (s): 22.2708
CPU time (s): 22.2426
CPU user time (s): 22.1186
CPU system time (s): 0.123981
CPU usage (%): 99.8736
Max. virtual memory (cumulated for all children) (Kb): 40256

Launcher Data (download as text)

Begin job on node11 on Fri Jun  2 04:01:40 UTC 2006


FILE ID= 39582-1149220900

PBS_JOBID= 295314

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  e4fb42fad6e5e99b3f9cfb09951614f4

RANDOM SEED= 782609159


/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.222
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	: 5931.00
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.222
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:       1561944 kB
Buffers:         33616 kB
Cached:         384380 kB
SwapCached:       3468 kB
Active:         149868 kB
Inactive:       277020 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1561944 kB
SwapTotal:     4192956 kB
SwapFree:      4181380 kB
Dirty:             204 kB
Writeback:           0 kB
Mapped:          14728 kB
Slab:            53124 kB
Committed_AS:   256464 kB
PageTables:       1484 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node11 on Fri Jun  2 04:02:02 UTC 2006