Trace number 34328

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
PB-smodels 1.28OPT100 0.323949 0.318087

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-100-2_0-yes1-1.opb
MD5SUM116a942422e9404c5d3cdfc29ea9d859
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark100
Best CPU time to get the best result obtained on this benchmark0.005998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 100
Optimality of the best value was proved YES
Number of variables200
Total number of constraints300
Number of constraints which are clauses299
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint3
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 2
Number of bits of the biggest number in a constraint 2
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

Solver Data (download as text)

0.00	c Running pbsmodels-v1.28
0.30	o 100
0.31	s OPTIMUM FOUND
0.31	v x2 x4 x6 x7 x10 x11 x13 x16 x18 x20 x21 x23 x26 x28 x29 x32 x34 x36 x37 x39 x41 x44 x46 x47 x49 x52 x54 x55 x58 x59 x61 x63 x66 x67 x69
0.31	v x72 x74 x75 x78 x80 x81 x83 x85 x88 x90 x91 x93 x95 x97 x99 x101 x104 x105 x108 x110 x112 x114 x116 x118 x119 x121 x124 x125 x128
0.31	v x129 x131 x134 x135 x138 x140 x141 x143 x145 x147 x149 x152 x153 x156 x158 x160 x161 x163 x165 x168 x169 x171 x174 x175 x178 x179
0.31	v x182 x183 x186 x187 x190 x191 x194 x195 x197 x199 -x1 -x3 -x5 -x8 -x9 -x12 -x14 -x15 -x17 -x19 -x22 -x24 -x25 -x27 -x30 -x31 -x33
0.31	v -x35 -x38 -x40 -x42 -x43 -x45 -x48 -x50 -x51 -x53 -x56 -x57 -x60 -x62 -x64 -x65 -x68 -x70 -x71 -x73 -x76 -x77 -x79 -x82 -x84 -x86
0.31	v -x87 -x89 -x92 -x94 -x96 -x98 -x100 -x102 -x103 -x106 -x107 -x109 -x111 -x113 -x115 -x117 -x120 -x122 -x123 -x126 -x127 -x130
0.31	v -x132 -x133 -x136 -x137 -x139 -x142 -x144 -x146 -x148 -x150 -x151 -x154 -x155 -x157 -x159 -x162 -x164 -x166 -x167 -x170 -x172
0.31	v -x173 -x176 -x177 -x180 -x181 -x184 -x185 -x188 -x189 -x192 -x193 -x196 -x198 -x200

Verifier Data (download as text)

OK	100

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

runsolver version 3.0.1 (c) roussel@cril.univ-artois.fr

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node9/watcher-34328-1149638571 -o ROOT/results/node9/solver-34328-1149638571 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node9/34328-1149638571/instance-34328-1149638571.opb 974003887 ROOT/tmp/node9/34328-1149638571 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.85 0.97 0.99 2/64 16841
/proc/meminfo: memFree=1954688/2055920 swapFree=4180524/4192956
[pid=16841] ppid=16839 vsize=5360 CPUtime=0
/proc/16841/stat : 16841 (runpbsmodels) R 16839 16841 16795 0 -1 4194304 266 0 0 0 0 0 0 0 19 0 1 0 229519452 5488640 233 18446744073709551615 4194304 4889804 548682069168 18446744073709551615 215418835681 0 0 4100 65536 0 0 0 17 1 0 0
/proc/16841/statm: 1340 233 194 169 0 51 0

Child status: 0
Real time (s): 0.318087
CPU time (s): 0.323949
CPU user time (s): 0.303953
CPU system time (s): 0.019996
CPU usage (%): 101.843
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node9 on Wed Jun  7 00:02:51 UTC 2006


FILE ID= 34328-1149638571

PBS_JOBID= 323147

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-100-2_0-yes1-1.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node9/34328-1149638571/instance-34328-1149638571.opb 974003887  ROOT/tmp/node9/34328-1149638571
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-34328-1149638571 -o ROOT/results/node9/solver-34328-1149638571 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node9/34328-1149638571/instance-34328-1149638571.opb 974003887  ROOT/tmp/node9/34328-1149638571

MD5SUM SOLVER= f639f6b7f53e3afd14340f75c0e271ee 82c14a26114306e436bf36ef1d1c85a0 c893ceb51a2aaa4ab2f96d97b043cdf0 8c810dcfce02286b111d075d14837741 79b233270d136fcdcf9d8f80d20efef0
MD5SUM BENCH=  116a942422e9404c5d3cdfc29ea9d859

RANDOM SEED= 974003887


/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.234
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.234
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:       1954960 kB
Buffers:         17100 kB
Cached:          47192 kB
SwapCached:       4728 kB
Active:          26600 kB
Inactive:        47068 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1954960 kB
SwapTotal:     4192956 kB
SwapFree:      4180524 kB
Dirty:             292 kB
Writeback:           0 kB
Mapped:          14296 kB
Slab:            13340 kB
Committed_AS:   429352 kB
PageTables:       1424 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node9 on Wed Jun  7 00:02:52 UTC 2006