Trace number 34381

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.28OPT75 0.075988 0.069881

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/primes-dimacs-cnf/normalized-par8-3-c.opb
MD5SUM336bc01fe64946233bd69e86063840df
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark75
Best CPU time to get the best result obtained on this benchmark0.003999
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 75
Optimality of the best value was proved YES
Number of variables150
Total number of constraints373
Number of constraints which are clauses373
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 constraint3
Number of terms in the objective function 150
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 150
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 150
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.05	o 75
0.06	s OPTIMUM FOUND
0.06	v x1 x4 x5 x8 x10 x12 x14 x16 x18 x20 x22 x24 x26 x28 x30 x32 x34 x36 x38 x40 x42 x44 x46 x48 x50 x52 x54 x56 x58 x60 x62 x63 x66 x68 x69
0.06	v x71 x73 x75 x77 x79 x81 x83 x86 x87 x90 x91 x93 x95 x97 x99 x102 x104 x105 x107 x109 x112 x113 x115 x118 x120 x121 x124 x126 x127
0.06	v x130 x131 x133 x135 x137 x139 x142 x143 x145 x148 x149 -x2 -x3 -x6 -x7 -x9 -x11 -x13 -x15 -x17 -x19 -x21 -x23 -x25 -x27 -x29 -x31
0.06	v -x33 -x35 -x37 -x39 -x41 -x43 -x45 -x47 -x49 -x51 -x53 -x55 -x57 -x59 -x61 -x64 -x65 -x67 -x70 -x72 -x74 -x76 -x78 -x80 -x82 -x84
0.06	v -x85 -x88 -x89 -x92 -x94 -x96 -x98 -x100 -x101 -x103 -x106 -x108 -x110 -x111 -x114 -x116 -x117 -x119 -x122 -x123 -x125 -x128
0.06	v -x129 -x132 -x134 -x136 -x138 -x140 -x141 -x144 -x146 -x147 -x150

Verifier Data (download as text)

OK	75

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/node7/watcher-34381-1149639207 -o ROOT/results/node7/solver-34381-1149639207 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node7/34381-1149639207/instance-34381-1149639207.opb 583267892 ROOT/tmp/node7/34381-1149639207 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.76 0.89 0.96 2/64 15832
/proc/meminfo: memFree=1980568/2055920 swapFree=4181340/4192956
[pid=15832] ppid=15830 vsize=5356 CPUtime=0
/proc/15832/stat : 15832 (runpbsmodels) R 15830 15832 15786 0 -1 4194304 184 0 0 0 0 0 0 0 19 0 1 0 229582912 5484544 153 18446744073709551615 4194304 4889804 548682069168 18446744073709551615 244671282674 0 0 4096 0 0 0 0 17 1 0 0
/proc/15832/statm: 1339 153 126 169 0 50 0

Child status: 0
Real time (s): 0.069881
CPU time (s): 0.075988
CPU user time (s): 0.049992
CPU system time (s): 0.025996
CPU usage (%): 108.739
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node7 on Wed Jun  7 00:13:27 UTC 2006


FILE ID= 34381-1149639207

PBS_JOBID= 323200

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-par8-3-c.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node7/34381-1149639207/instance-34381-1149639207.opb 583267892  ROOT/tmp/node7/34381-1149639207
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node7/watcher-34381-1149639207 -o ROOT/results/node7/solver-34381-1149639207 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node7/34381-1149639207/instance-34381-1149639207.opb 583267892  ROOT/tmp/node7/34381-1149639207

MD5SUM SOLVER= f639f6b7f53e3afd14340f75c0e271ee 82c14a26114306e436bf36ef1d1c85a0 c893ceb51a2aaa4ab2f96d97b043cdf0 8c810dcfce02286b111d075d14837741 79b233270d136fcdcf9d8f80d20efef0
MD5SUM BENCH=  336bc01fe64946233bd69e86063840df

RANDOM SEED= 583267892


/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.232
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.232
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:       1980776 kB
Buffers:          5836 kB
Cached:          22852 kB
SwapCached:       3476 kB
Active:          17132 kB
Inactive:        20420 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1980776 kB
SwapTotal:     4192956 kB
SwapFree:      4181340 kB
Dirty:             272 kB
Writeback:           0 kB
Mapped:          14284 kB
Slab:            23560 kB
Committed_AS:   392412 kB
PageTables:       1480 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node7 on Wed Jun  7 00:13:27 UTC 2006