Trace number 49628

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.28OPT6 0.050991 0.054377

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
bounded_golomb_rulers/normalized-bogr_4.opb
MD5SUMe07d1b5f59078d7e9ac49c5c9d354a5d
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark6
Best CPU time to get the best result obtained on this benchmark0.002998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 6
Optimality of the best value was proved YES
Number of variables38
Total number of constraints44
Number of constraints which are clauses1
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints43
Minimum length of a constraint1
Maximum length of a constraint18
Number of terms in the objective function 5
Biggest coefficient in the objective function 8
Number of bits for the biggest coefficient in the objective function 4
Sum of the numbers in the objective function 21
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 32
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 114
Number of bits of the biggest sum of numbers7
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 Running pbsmodels-v1.28
0.03	o 13
0.04	o 12
0.04	o 11
0.04	o 9
0.04	o 8
0.04	o 6
0.05	s OPTIMUM FOUND
0.05	v x38 x5 x15 x33 x32 x29 x27 x26 x25 x24 x23 x22 x21 x20 x19 x18 -x1 -x2 -x3 -x4 -x6 -x7 -x8 -x14 -x16 -x17 -x37 -x9 -x10 -x11 -x12 -x13
0.05	v -x36 -x35 -x34 -x31 -x30 -x28

Verifier Data (download as text)

OK	6

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/node74/watcher-49628-1149937903 -o ROOT/results/node74/solver-49628-1149937903 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node74/49628-1149937903/instance-49628-1149937903.opb 94942119 ROOT/tmp/node74/49628-1149937903 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.00 0.00 0.06 3/64 3680
/proc/meminfo: memFree=1747824/2055920 swapFree=4182268/4192956
[pid=3680] ppid=3678 vsize=5360 CPUtime=0
/proc/3680/stat : 3680 (runpbsmodels) S 3678 3680 3634 0 -1 4194304 286 0 0 0 0 0 0 0 19 0 1 0 259454583 5488640 234 18446744073709551615 4194304 4889804 548682069168 18446744073709551615 218076078916 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/3680/statm: 1340 234 195 169 0 51 0
[pid=3681] ppid=3680 vsize=124 CPUtime=0
/proc/3681/stat : 3681 (pbsmodels-v1.28) R 3680 3680 3634 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 259454583 126976 23 18446744073709551615 4194304 4206940 548682069008 18446744073709551615 218073462037 0 0 4096 0 0 0 0 17 1 0 0
/proc/3681/statm: 31 23 17 3 0 3 0

Child status: 0
Real time (s): 0.054377
CPU time (s): 0.050991
CPU user time (s): 0.029995
CPU system time (s): 0.020996
CPU usage (%): 93.7731
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node74 on Sat Jun 10 11:11:43 UTC 2006


FILE ID= 49628-1149937903

PBS_JOBID= 385638

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/bounded_golomb_rulers/normalized-bogr_4.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node74/49628-1149937903/instance-49628-1149937903.opb 94942119  ROOT/tmp/node74/49628-1149937903
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node74/watcher-49628-1149937903 -o ROOT/results/node74/solver-49628-1149937903 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node74/49628-1149937903/instance-49628-1149937903.opb 94942119  ROOT/tmp/node74/49628-1149937903

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

RANDOM SEED= 94942119


/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.274
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.274
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:       1748096 kB
Buffers:         34956 kB
Cached:         200780 kB
SwapCached:       2400 kB
Active:          40480 kB
Inactive:       204012 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1748096 kB
SwapTotal:     4192956 kB
SwapFree:      4182268 kB
Dirty:             128 kB
Writeback:           0 kB
Mapped:          15780 kB
Slab:            49436 kB
Committed_AS:   639536 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node74 on Sat Jun 10 11:11:43 UTC 2006