Trace number 39581

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 1.71474 1.72423

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900559365.opb
MD5SUM924af7c450ed428ac078913fd23bc162
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 benchmark1.25881
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 691
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.074
0.08	c After prepocess the problem consists of 231 variables and 2586 constraints.
0.12	c Restart #1 #Var: 231 LB: 0 @ 0.117
0.25	c Restart #2 #Var: 231 LB: 0 @ 0.245
0.40	c Restart #3 #Var: 231 LB: 0 @ 0.392
0.59	c Restart #4 #Var: 231 LB: 0 @ 0.587
0.84	c Restart #5 #Var: 231 LB: 0 @ 0.832
1.10	c Restart #6 #Var: 231 LB: 0 @ 1.094
1.43	c Restart #7 #Var: 231 LB: 0 @ 1.429
1.72	c Sol. found (all assignments made)...
1.72	o 0
1.72	c NEW SOLUTION FOUND: 0 @ 1.71
1.72	s SATISFIABLE
1.72	c Cost: 0
1.72	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
1.72	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
1.72	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
1.72	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
1.72	v -x107 x108 -x109 -x110 -x111 x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 -x132 -x142 -x152 -x162 x172 -x182
1.72	v -x192 -x202 -x212 -x222 -x122 -x143 -x153 -x163 -x173 -x183 -x193 x203 -x213 -x223 x123 -x133 -x154 -x164 -x174 -x184 -x194
1.72	v -x204 -x214 -x224 -x124 -x134 -x144 x165 -x175 -x185 -x195 -x205 -x215 -x225 -x125 -x135 -x145 -x155 -x176 -x186 -x196 -x206
1.72	v -x216 x226 -x126 -x136 -x146 -x156 -x166 -x187 x197 -x207 -x217 -x227 -x127 -x137 -x147 -x157 -x167 -x177 -x198 -x208 x218
1.72	v -x228 -x128 x138 -x148 -x158 -x168 -x178 -x188 -x209 -x219 -x229 -x129 -x139 -x149 -x159 -x169 -x179 x189 -x199 -x220 -x230
1.72	v -x130 -x140 -x150 x160 -x170 -x180 -x190 -x200 -x210 -x231 -x131 -x141 x151 -x161 -x171 -x181 -x191 -x201 -x211 -x221
1.72	c Exit Code: 10
1.72	c Total time: 1.711 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/node77/watcher-39581-1149220847 -o ROOT/results/node77/solver-39581-1149220847 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node77/39581-1149220847/instance-39581-1149220847.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.96 0.96 2/67 24490
/proc/meminfo: memFree=1666976/2055892 swapFree=4085336/4096564
[pid=24490] ppid=24488 vsize=4672 CPUtime=0
/proc/24490/stat : 24490 (bsolo) R 24488 24490 24445 0 -1 0 155 0 0 0 0 0 0 0 19 0 1 0 187723916 4784128 136 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 1432472 0 0 4096 0 0 0 0 17 1 0 0
/proc/24490/statm: 1168 137 106 55 0 46 0

Child status: 10
Real time (s): 1.72423
CPU time (s): 1.71474
CPU user time (s): 1.69174
CPU system time (s): 0.022996
CPU usage (%): 99.4493
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node77 on Fri Jun  2 04:00:47 UTC 2006


FILE ID= 39581-1149220847

PBS_JOBID= 295301

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  924af7c450ed428ac078913fd23bc162

RANDOM SEED= 774719936


/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.238
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.16
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.238
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.41
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1667248 kB
Buffers:         32096 kB
Cached:         290232 kB
SwapCached:       2644 kB
Active:          94792 kB
Inactive:       236396 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1667248 kB
SwapTotal:     4096564 kB
SwapFree:      4085336 kB
Dirty:             172 kB
Writeback:           0 kB
Mapped:          16108 kB
Slab:            44148 kB
Committed_AS:   202968 kB
PageTables:       1276 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node77 on Fri Jun  2 04:00:49 UTC 2006