Trace number 40722

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 NameAnswerObjective functionCPU timeWall clock time
bsolo 2006/05OPT1077181440 16.2365 16.3024

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/MIPLIB/
miplib/normalized-mps-v2-20-10-misc03.opb
MD5SUM25aef4d44af7e0ab52082ae8b5eea91f
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark1077181440
Best CPU time to get the best result obtained on this benchmark16.2365
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 1077181440
Optimality of the best value was proved YES
Number of variables190
Total number of constraints96
Number of constraints which are clauses31
Number of constraints which are cardinality constraints (but not clauses)11
Number of constraints which are nor clauses,nor cardinality constraints54
Minimum length of a constraint6
Maximum length of a constraint169
Number of terms in the objective function 31
Biggest coefficient in the objective function 1073741824
Number of bits for the biggest coefficient in the objective function 31
Sum of the numbers in the objective function 2147483647
Number of bits of the sum of numbers in the objective function 31
Biggest number in a constraint 1073741824
Number of bits of the biggest number in a constraint 31
Biggest sum of numbers in a constraint 3287149567
Number of bits of the biggest sum of numbers32
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.00	c Time Limit set via PBTIMEOUT to 1800
0.06	c INFO: OSL Context initialized.
0.06	c BIG Int formula...
0.07	c Initial problem consists of 190 variables and 123 constraints.
0.07	c No problem reductions applied in OPT. instance.
0.07	c	preprocess terminated. Elapsed time: 0.019
0.07	c After prepocess the problem consists of 190 variables and 123 constraints.
0.07	c Initial Lower Bound: 0
0.09	c Restart #1 #Var: 190 LB: 0 @ 0.044
0.16	c Restart #2 #Var: 190 LB: 0 @ 0.113
0.30	c Restart #3 #Var: 190 LB: 0 @ 0.244
0.48	c Restart #4 #Var: 190 LB: 0 @ 0.426
0.63	c Restart #5 #Var: 190 LB: 0 @ 0.58
0.83	c Restart #6 #Var: 190 LB: 0 @ 0.776
1.05	c Restart #7 #Var: 190 LB: 0 @ 1.003
1.31	c Restart #8 #Var: 190 LB: 0 @ 1.259
1.58	c Restart #9 #Var: 190 LB: 0 @ 1.52
1.88	c Restart #10 #Var: 190 LB: 0 @ 1.821
2.21	c Restart #11 #Var: 190 LB: 0 @ 2.151
2.24	c Sol. found (all assignments made)...
2.24	o 1079982080
2.24	c NEW SOLUTION FOUND: 1079982080 @ 2.19
2.25	c Sol. found (all assignments made)...
2.25	o 1079654400
2.25	c NEW SOLUTION FOUND: 1079654400 @ 2.19
2.25	c Sol. found (all assignments made)...
2.25	o 1079577600
2.25	c NEW SOLUTION FOUND: 1079577600 @ 2.191
2.25	c Sol. found (all assignments made)...
2.25	o 1079070720
2.25	c NEW SOLUTION FOUND: 1079070720 @ 2.191
2.25	c Sol. found (all assignments made)...
2.25	o 1078993920
2.25	c NEW SOLUTION FOUND: 1078993920 @ 2.192
2.25	c Sol. found (all assignments made)...
2.25	o 1078932480
2.25	c NEW SOLUTION FOUND: 1078932480 @ 2.199
2.26	c Sol. found (all assignments made)...
2.26	o 1078528000
2.26	c NEW SOLUTION FOUND: 1078528000 @ 2.203
2.26	c Sol. found (all assignments made)...
2.26	c Sol. found (all assignments made)...
2.26	o 1078021120
2.26	c NEW SOLUTION FOUND: 1078021120 @ 2.204
2.26	c Sol. found (all assignments made)...
2.26	o 1077944320
2.26	c NEW SOLUTION FOUND: 1077944320 @ 2.204
2.34	c Sol. found (all assignments made)...
2.35	c Sol. found (all assignments made)...
2.35	o 1077739520
2.35	c NEW SOLUTION FOUND: 1077739520 @ 2.292
2.56	c Sol. found (all assignments made)...
2.56	o 1077544960
2.56	c NEW SOLUTION FOUND: 1077544960 @ 2.502
2.56	c Sol. found (all assignments made)...
2.56	o 1077468160
2.56	c NEW SOLUTION FOUND: 1077468160 @ 2.502
2.61	c Sol. found (all assignments made)...
2.96	c Sol. found (all assignments made)...
2.96	o 1077181440
2.96	c NEW SOLUTION FOUND: 1077181440 @ 2.904
2.96	c Sol. found (all assignments made)...
3.84	c Restart #12 #Var: 178 LB: 1073741824 @ 3.783
4.65	c Restart #13 #Var: 176 LB: 1073741824 @ 4.591
5.73	c Restart #14 #Var: 176 LB: 1073741824 @ 5.669
7.12	c Restart #15 #Var: 175 LB: 1073741824 @ 7.061
9.16	c CHANGE to MIS mode... 	UB: 1077181440	MIS: 1075838976	LPR: -2147483648 (0)	Diff: -0.50098
9.16	c Restart #0 #Var: 169 LB: 1075838976 @ 9.099
9.30	c Restart #1 #Var: 169 LB: 1075838976 @ 9.243
9.52	c Restart #2 #Var: 168 LB: 1075838976 @ 9.457
9.89	c Restart #3 #Var: 167 LB: 1075838976 @ 9.827
10.30	c Restart #4 #Var: 167 LB: 1075838976 @ 10.244
10.80	c Restart #5 #Var: 166 LB: 1075838976 @ 10.74
11.37	c Restart #6 #Var: 166 LB: 1075838976 @ 11.311
11.94	c Restart #7 #Var: 166 LB: 1075838976 @ 11.883
12.86	c Restart #8 #Var: 166 LB: 1075838976 @ 12.8
13.99	c Restart #9 #Var: 165 LB: 1075838976 @ 13.928
15.35	c Restart #10 #Var: 143 LB: 1075838976 @ 15.29
16.29	s OPTIMUM FOUND
16.29	c Cost: 1077181440
16.29	v -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167 -x168 -x169 x170 x171 x172 x173 x174 -x175 -x176 -x177 x178 -x179 x180 x181
16.29	v -x182 -x183 -x184 -x185 -x186 -x187 -x188 -x189 x190 -x4 -x5 -x6 -x7 -x8 -x9 -x10 -x11 -x12 -x13 -x14 -x15 -x16 -x17 -x18 x19
16.29	v -x20 -x21 x22 -x23 -x24 -x28 -x29 -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48
16.29	v -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x60 -x61 x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x76 -x77 -x78 -x79 -x80
16.29	v x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 x96 -x100 -x101 -x102 -x103 -x104 -x105 -x106 -x107
16.29	v -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 x120 -x124 -x125 -x126 -x127 -x128 -x129 x130 -x131
16.29	v -x132 -x133 x134 -x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 x148 x149 -x150 x151 -x152 x153 -x154 x155 x156
16.29	v -x157 x158 -x159 -x1 -x2 -x3 -x25 -x26 -x27 -x49 -x50 -x51 -x73 -x74 -x75 -x97 -x98 -x99 -x121 -x122 -x123 -x145 -x146 -x147
16.29	c Exit Code: 30
16.29	c Total time: 16.229 s

Verifier Data (download as text)

OK	1077181440

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.98 2/64 3205
/proc/meminfo: memFree=1714608/2055920 swapFree=4192948/4192956
[pid=3205] ppid=3203 vsize=3364 CPUtime=0
/proc/3205/stat : 3205 (bsolo) R 3203 3205 3159 0 -1 0 60 0 0 0 0 0 0 0 19 0 1 0 33417772 3444736 43 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4870948 0 0 4096 0 0 0 0 17 1 0 0
/proc/3205/statm: 859 43 32 55 0 40 0

[startup+10.0031 s]
/proc/loadavg: 0.93 0.95 0.98 2/64 3205
/proc/meminfo: memFree=1696136/2055920 swapFree=4192948/4192956
[pid=3205] ppid=3203 vsize=22932 CPUtime=9.93
/proc/3205/stat : 3205 (bsolo) R 3203 3205 3159 0 -1 0 5007 0 0 0 988 5 0 0 25 0 1 0 33417772 23482368 4922 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134534809 0 0 4096 16384 0 0 0 17 1 0 0
/proc/3205/statm: 5733 4922 298 55 0 4625 0
Current children cumulated CPU time (s) 9.93
Current children cumulated vsize (Kb) 22932

Child status: 30
Real time (s): 16.3024
CPU time (s): 16.2365
CPU user time (s): 16.1445
CPU system time (s): 0.091986
CPU usage (%): 99.5962
Max. virtual memory (cumulated for all children) (Kb): 22932

Launcher Data (download as text)

Begin job on node58 on Sat Jun  3 05:48:29 UTC 2006


FILE ID= 40722-1149313709

PBS_JOBID= 308203

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-BIGINT/mps-v2-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-misc03.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node58/40722-1149313709/instance-40722-1149313709.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node58/watcher-40722-1149313709 -o ROOT/results/node58/solver-40722-1149313709 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node58/40722-1149313709/instance-40722-1149313709.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  25aef4d44af7e0ab52082ae8b5eea91f

RANDOM SEED= 420290877


/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.276
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.276
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:       1714816 kB
Buffers:         24864 kB
Cached:         240532 kB
SwapCached:          8 kB
Active:          57156 kB
Inactive:       222752 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1714816 kB
SwapTotal:     4192956 kB
SwapFree:      4192948 kB
Dirty:             140 kB
Writeback:           0 kB
Mapped:          24920 kB
Slab:            47248 kB
Committed_AS:   215592 kB
PageTables:       1392 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node58 on Sat Jun  3 05:48:45 UTC 2006