Trace number 36927

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
Pueblo 1.4OPT89 1.86072 1.86675

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/primes-dimacs-cnf/normalized-jnh217.opb
MD5SUM5f8256f2423d7410846942dcc96981a5
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark89
Best CPU time to get the best result obtained on this benchmark0.556914
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 89
Optimality of the best value was proved YES
Number of variables200
Total number of constraints900
Number of constraints which are clauses900
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint11
Number of terms in the objective function 200
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 200
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 200
Number of bits of the biggest sum of numbers8
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 Pueblo version 1.4 (September 2005)
0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
0.02	c starting to Solve
0.02	c #variables read: 200 - #constraints read: 901
0.02	o 97
0.03	o 96
0.03	o 92
0.04	o 91
0.17	o 90
0.70	o 89
1.86	c optimum objective found = 89
1.86	c total time              : 1.85 s
1.86	s OPTIMUM FOUND
1.86	v -x1 x2 -x3 x4 -x5 x6 x7 -x8 x9 -x10 -x11 x12 x13 -x14 -x15 x16 -x17 x18 -x19 -x20 x21 -x22 -x23 x24 x25 -x26 x27 -x28 x29 -x30 -x31
1.86	v x32 x33 -x34 -x35 -x36 -x37 x38 -x39 x40 -x41 -x42 -x43 -x44 -x45 x46 -x47 -x48 -x49 x50 x51 -x52 x53 -x54 -x55 x56 x57 -x58 x59
1.86	v -x60 -x61 -x62 x63 -x64 -x65 x66 x67 -x68 -x69 x70 x71 -x72 x73 -x74 x75 -x76 x77 -x78 x79 -x80 -x81 x82 -x83 x84 x85 -x86 -x87 x88
1.86	v -x89 x90 -x91 x92 x93 -x94 x95 -x96 x97 -x98 -x99 x100 -x101 -x102 -x103 x104 x105 -x106 -x107 x108 x109 -x110 x111 -x112 -x113
1.86	v -x114 -x115 x116 x117 -x118 -x119 x120 x121 -x122 x123 -x124 -x125 x126 -x127 x128 x129 -x130 -x131 -x132 x133 -x134 -x135
1.86	v x136 x137 -x138 -x139 -x140 x141 -x142 x143 -x144 x145 -x146 x147 -x148 x149 -x150 -x151 x152 -x153 x154 x155 -x156 -x157 x158
1.86	v x159 -x160 -x161 x162 x163 -x164 x165 -x166 -x167 x168 -x169 x170 x171 -x172 x173 -x174 x175 -x176 -x177 x178 -x179 -x180 x181
1.86	v -x182 x183 -x184 x185 -x186 x187 -x188 x189 -x190 x191 -x192 x193 -x194 -x195 x196 x197 -x198 x199 -x200

Verifier Data (download as text)

OK	89

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/node88/watcher-36927-1149418000 -o ROOT/results/node88/solver-36927-1149418000 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node88/36927-1149418000/instance-36927-1149418000.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 1.00 1.00 1.00 2/68 14739
/proc/meminfo: memFree=1447216/2055888 swapFree=4085336/4096564
[pid=14739] ppid=14737 vsize=2336 CPUtime=0
/proc/14739/stat : 14739 (Pueblo) R 14737 14739 14693 0 -1 4194304 70 0 0 0 0 0 0 0 18 0 1 0 207439139 2392064 55 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 9483539 0 0 4096 0 0 0 0 17 1 0 0
/proc/14739/statm: 584 67 53 16 0 11 0

Child status: 30
Real time (s): 1.86675
CPU time (s): 1.86072
CPU user time (s): 1.85372
CPU system time (s): 0.006998
CPU usage (%): 99.6766
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node88 on Sun Jun  4 10:46:40 UTC 2006


FILE ID= 36927-1149418000

PBS_JOBID= 315505

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-jnh217.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node88/36927-1149418000/instance-36927-1149418000.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node88/watcher-36927-1149418000 -o ROOT/results/node88/solver-36927-1149418000 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node88/36927-1149418000/instance-36927-1149418000.opb

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  5f8256f2423d7410846942dcc96981a5

RANDOM SEED= 905300068


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


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1447552 kB
Buffers:         30588 kB
Cached:         505736 kB
SwapCached:       2304 kB
Active:          94788 kB
Inactive:       450056 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1447552 kB
SwapTotal:     4096564 kB
SwapFree:      4085336 kB
Dirty:             152 kB
Writeback:           0 kB
Mapped:          16804 kB
Slab:            50060 kB
Committed_AS:   399288 kB
PageTables:       1280 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node88 on Sun Jun  4 10:46:42 UTC 2006