Trace number 39553

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 20.8148 20.8441

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 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.09	c Using non-optimization problem switches.
0.09	c No problem reductions applied in OPT. instance.
0.09	c	preprocess terminated. Elapsed time: 0.071
0.09	c After prepocess the problem consists of 231 variables and 2586 constraints.
0.12	c Restart #1 #Var: 231 LB: 0 @ 0.109
0.22	c Restart #2 #Var: 231 LB: 0 @ 0.202
0.36	c Restart #3 #Var: 231 LB: 0 @ 0.35
0.54	c Restart #4 #Var: 231 LB: 0 @ 0.526
0.73	c Restart #5 #Var: 231 LB: 0 @ 0.719
1.02	c Restart #6 #Var: 231 LB: 0 @ 1.008
1.33	c Restart #7 #Var: 231 LB: 0 @ 1.316
1.69	c Restart #8 #Var: 231 LB: 0 @ 1.673
2.10	c Restart #9 #Var: 231 LB: 0 @ 2.089
2.59	c Restart #10 #Var: 231 LB: 0 @ 2.571
3.16	c Restart #11 #Var: 231 LB: 0 @ 3.147
3.78	c Restart #12 #Var: 231 LB: 0 @ 3.765
4.39	c Restart #13 #Var: 231 LB: 0 @ 4.372
5.16	c Restart #14 #Var: 231 LB: 0 @ 5.149
6.09	c Restart #15 #Var: 231 LB: 0 @ 6.076
7.27	c Restart #16 #Var: 231 LB: 0 @ 7.251
8.52	c Restart #17 #Var: 231 LB: 0 @ 8.505
9.96	c Restart #18 #Var: 231 LB: 0 @ 9.945
12.04	c Restart #19 #Var: 231 LB: 0 @ 12.022
13.93	c Restart #20 #Var: 231 LB: 0 @ 13.911
16.41	c Restart #21 #Var: 231 LB: 0 @ 16.39
19.72	c Restart #22 #Var: 231 LB: 0 @ 19.696
20.83	c Sol. found (all assignments made)...
20.83	o 0
20.83	c NEW SOLUTION FOUND: 0 @ 20.806
20.83	s SATISFIABLE
20.83	c Cost: 0
20.83	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
20.83	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
20.83	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
20.83	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
20.83	v -x107 -x108 -x109 -x110 x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 -x132 -x142 -x152 x162 -x172 -x182
20.83	v -x192 -x202 -x212 -x222 -x122 -x143 -x153 -x163 -x173 -x183 x193 -x203 -x213 -x223 -x123 -x133 -x154 -x164 -x174 -x184 -x194
20.83	v -x204 -x214 x224 -x124 -x134 -x144 -x165 -x175 x185 -x195 -x205 -x215 -x225 -x125 -x135 x145 -x155 -x176 -x186 -x196 -x206
20.83	v -x216 -x226 -x126 -x136 -x146 -x156 -x166 -x187 -x197 -x207 x217 -x227 -x127 -x137 -x147 -x157 -x167 -x177 -x198 x208 -x218
20.83	v -x228 -x128 -x138 -x148 x158 -x168 -x178 -x188 -x209 -x219 -x229 x129 -x139 -x149 -x159 -x169 -x179 -x189 -x199 -x220 -x230
20.83	v -x130 x140 -x150 -x160 -x170 -x180 -x190 -x200 -x210 -x231 -x131 -x141 -x151 -x161 -x171 x181 -x191 -x201 -x211 -x221
20.83	c Exit Code: 10
20.83	c Total time: 20.807 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/node5/watcher-39553-1149217487 -o ROOT/results/node5/solver-39553-1149217487 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node5/39553-1149217487/instance-39553-1149217487.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.79 0.95 0.91 3/64 21343
/proc/meminfo: memFree=1471968/2055920 swapFree=4180912/4192956
[pid=21343] ppid=21341 vsize=4664 CPUtime=0
/proc/21343/stat : 21343 (bsolo) R 21341 21343 21298 0 -1 0 82 0 0 0 0 0 0 0 18 0 1 0 187352404 4775936 64 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 7895693 0 0 4096 0 0 0 0 17 1 0 0
/proc/21343/statm: 1166 79 62 55 0 46 0

[startup+10.0018 s]
/proc/loadavg: 0.83 0.95 0.91 2/64 21343
/proc/meminfo: memFree=1449696/2055920 swapFree=4180912/4192956
[pid=21343] ppid=21341 vsize=26660 CPUtime=9.97
/proc/21343/stat : 21343 (bsolo) R 21341 21343 21298 0 -1 0 5938 0 0 0 992 5 0 0 25 0 1 0 187352404 27299840 5853 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134718704 0 0 4096 16384 0 0 0 17 1 0 0
/proc/21343/statm: 6665 5853 296 55 0 5557 0
Current children cumulated CPU time (s) 9.97
Current children cumulated vsize (Kb) 26660

[startup+20.0078 s]
/proc/loadavg: 0.85 0.95 0.91 2/64 21343
/proc/meminfo: memFree=1439392/2055920 swapFree=4180912/4192956
[pid=21343] ppid=21341 vsize=36956 CPUtime=19.97
/proc/21343/stat : 21343 (bsolo) R 21341 21343 21298 0 -1 0 8506 0 0 0 1987 10 0 0 25 0 1 0 187352404 37842944 8421 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134534127 0 0 4096 16384 0 0 0 17 1 0 0
/proc/21343/statm: 9239 8421 296 55 0 8131 0
Current children cumulated CPU time (s) 19.97
Current children cumulated vsize (Kb) 36956

Child status: 10
Real time (s): 20.8441
CPU time (s): 20.8148
CPU user time (s): 20.7009
CPU system time (s): 0.113982
CPU usage (%): 99.8598
Max. virtual memory (cumulated for all children) (Kb): 36956

Launcher Data (download as text)

Begin job on node5 on Fri Jun  2 03:04:47 UTC 2006


FILE ID= 39553-1149217487

PBS_JOBID= 294939

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  b3be50396cebacd2fb0dd8b51b7d346c

RANDOM SEED= 392728501


/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.279
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.279
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:       1472176 kB
Buffers:         34036 kB
Cached:         473552 kB
SwapCached:       4180 kB
Active:         204768 kB
Inactive:       311888 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1472176 kB
SwapTotal:     4192956 kB
SwapFree:      4180912 kB
Dirty:             304 kB
Writeback:           0 kB
Mapped:          14940 kB
Slab:            53168 kB
Committed_AS:   195052 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node5 on Fri Jun  2 03:05:08 UTC 2006