Trace number 39595

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 26.242 26.2624

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900547461.opb
MD5SUM851f60b4bba13dc8ad4e48be942c1c37
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.822874
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 695
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.01	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.073
0.08	c After prepocess the problem consists of 231 variables and 2586 constraints.
0.12	c Restart #1 #Var: 231 LB: 0 @ 0.113
0.29	c Restart #2 #Var: 231 LB: 0 @ 0.279
0.52	c Restart #3 #Var: 231 LB: 0 @ 0.516
0.66	c Restart #4 #Var: 231 LB: 0 @ 0.652
0.85	c Restart #5 #Var: 231 LB: 0 @ 0.845
1.13	c Restart #6 #Var: 231 LB: 0 @ 1.119
1.41	c Restart #7 #Var: 231 LB: 0 @ 1.403
1.76	c Restart #8 #Var: 231 LB: 0 @ 1.753
2.22	c Restart #9 #Var: 231 LB: 0 @ 2.209
2.79	c Restart #10 #Var: 231 LB: 0 @ 2.78
3.28	c Restart #11 #Var: 231 LB: 0 @ 3.276
3.96	c Restart #12 #Var: 231 LB: 0 @ 3.958
4.65	c Restart #13 #Var: 231 LB: 0 @ 4.641
5.59	c Restart #14 #Var: 231 LB: 0 @ 5.578
6.51	c Restart #15 #Var: 231 LB: 0 @ 6.502
7.78	c Restart #16 #Var: 231 LB: 0 @ 7.769
8.86	c Restart #17 #Var: 231 LB: 0 @ 8.855
10.54	c Restart #18 #Var: 231 LB: 0 @ 10.525
12.20	c Restart #19 #Var: 231 LB: 0 @ 12.182
14.40	c Restart #20 #Var: 231 LB: 0 @ 14.385
16.96	c Restart #21 #Var: 231 LB: 0 @ 16.947
19.19	c Restart #22 #Var: 231 LB: 0 @ 19.173
21.91	c Restart #23 #Var: 231 LB: 0 @ 21.892
24.23	c Restart #24 #Var: 231 LB: 0 @ 24.21
26.25	c Sol. found (all assignments made)...
26.25	o 0
26.25	c NEW SOLUTION FOUND: 0 @ 26.232
26.25	s SATISFIABLE
26.25	c Cost: 0
26.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
26.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
26.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 -x81
26.25	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
26.25	v -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 x116 -x117 -x118 -x119 -x120 -x121 -x132 -x142 -x152 -x162 -x172 -x182
26.25	v x192 -x202 -x212 -x222 -x122 -x143 -x153 -x163 -x173 -x183 -x193 -x203 -x213 x223 -x123 -x133 -x154 -x164 -x174 -x184 -x194
26.25	v -x204 x214 -x224 -x124 -x134 -x144 x165 -x175 -x185 -x195 -x205 -x215 -x225 x125 -x135 -x145 -x155 -x176 -x186 -x196 -x206
26.25	v -x216 -x226 -x126 -x136 -x146 x156 -x166 -x187 -x197 -x207 -x217 -x227 -x127 -x137 -x147 -x157 -x167 x177 -x198 -x208 -x218
26.25	v -x228 -x128 x138 -x148 -x158 -x168 -x178 -x188 -x209 -x219 -x229 -x129 -x139 -x149 -x159 -x169 -x179 x189 -x199 -x220 -x230
26.25	v -x130 -x140 -x150 -x160 -x170 -x180 -x190 -x200 x210 -x231 -x131 -x141 x151 -x161 -x171 -x181 -x191 -x201 -x211 -x221
26.25	c Exit Code: 10
26.25	c Total time: 26.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/node10/watcher-39595-1149222124 -o ROOT/results/node10/solver-39595-1149222124 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node10/39595-1149222124/instance-39595-1149222124.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/64 11268
/proc/meminfo: memFree=1457600/2055920 swapFree=4181412/4192956
[pid=11268] ppid=11266 vsize=3436 CPUtime=0
/proc/11268/stat : 11268 (bsolo) R 11266 11268 11223 0 -1 0 67 0 0 0 0 0 0 0 18 0 1 0 187874796 3518464 50 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 8892864 0 0 4096 0 0 0 0 17 1 0 0
/proc/11268/statm: 1156 55 41 55 0 44 0

[startup+10.0023 s]
/proc/loadavg: 0.93 0.95 0.90 2/64 11268
/proc/meminfo: memFree=1435672/2055920 swapFree=4181412/4192956
[pid=11268] ppid=11266 vsize=26784 CPUtime=9.98
/proc/11268/stat : 11268 (bsolo) R 11266 11268 11223 0 -1 0 5946 0 0 0 991 7 0 0 25 0 1 0 187874796 27426816 5861 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134718704 0 0 4096 16384 0 0 0 17 1 0 0
/proc/11268/statm: 6696 5861 296 55 0 5588 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 26784

[startup+20.0086 s]
/proc/loadavg: 0.94 0.96 0.91 2/64 11268
/proc/meminfo: memFree=1423264/2055920 swapFree=4181412/4192956
[pid=11268] ppid=11266 vsize=39196 CPUtime=19.99
/proc/11268/stat : 11268 (bsolo) R 11266 11268 11223 0 -1 0 9052 0 0 0 1989 10 0 0 25 0 1 0 187874796 40136704 8967 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134542121 0 0 4096 16384 0 0 0 17 1 0 0
/proc/11268/statm: 9799 8967 296 55 0 8691 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 39196

Child status: 10
Real time (s): 26.2624
CPU time (s): 26.242
CPU user time (s): 26.102
CPU system time (s): 0.139978
CPU usage (%): 99.9222
Max. virtual memory (cumulated for all children) (Kb): 39196

Launcher Data (download as text)

Begin job on node10 on Fri Jun  2 04:22:04 UTC 2006


FILE ID= 39595-1149222124

PBS_JOBID= 295490

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  851f60b4bba13dc8ad4e48be942c1c37

RANDOM SEED= 139938825


/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.236
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.236
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:       1457872 kB
Buffers:         27484 kB
Cached:         497580 kB
SwapCached:       3636 kB
Active:          82296 kB
Inactive:       451912 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1457872 kB
SwapTotal:     4192956 kB
SwapFree:      4181412 kB
Dirty:             184 kB
Writeback:           0 kB
Mapped:          14920 kB
Slab:            49856 kB
Committed_AS:   221248 kB
PageTables:       1412 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node10 on Fri Jun  2 04:22:30 UTC 2006