Trace number 48502

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
PBS 4.1LOPT149 0.014996 0.0178711

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/
factor/normalized-factor-size=9-P=149-Q=167.opb
MD5SUM1f78971d13423a3a94987e1d1496bfe5
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark149
Best CPU time to get the best result obtained on this benchmark0.014996
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 149
Optimality of the best value was proved YES
Number of variables99
Total number of constraints244
Number of constraints which are clauses243
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 constraint81
Number of terms in the objective function 9
Biggest coefficient in the objective function 256
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 511
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 65536
Number of bits of the biggest number in a constraint 17
Biggest sum of numbers in a constraint 286004
Number of bits of the biggest sum of numbers19
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 PBS v4 by Bashar Al-Rawi & Fadi Aloul
0.00	c Solving ROOT/tmp/node61/48502-1149850758/instance-48502-1149850758.opb ......
0.01	c done parsing opb.
0.01	o 149
0.01	o 149
0.01	s OPTIMUM FOUND
0.01	c Total Run Time					0.011998
0.01	v x1 x10 x11 x12 -x13 -x14 x15 -x16 x17 -x18 x19 -x2 x20 x21 -x22 -x23 x24 -x25 x26 -x27 -x28 -x29 x3 -x30 -x31 -x32 -x33 -x34 -x35
0.01	v -x36 x37 x38 x39 -x4 -x40 -x41 x42 -x43 x44 -x45 -x46 -x47 -x48 -x49 x5 -x50 -x51 -x52 -x53 -x54 x55 x56 x57 -x58 -x59 -x6 x60 -x61
0.01	v x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x7 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79 x8 -x80 -x81 x82 x83 x84 -x85 -x86
0.01	v x87 -x88 x89 -x9 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99

Verifier Data (download as text)

OK	149

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/node61/watcher-48502-1149850758 -o ROOT/results/node61/solver-48502-1149850758 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node61/48502-1149850758/instance-48502-1149850758.opb 349499124 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/64 18774
/proc/meminfo: memFree=1810104/2055920 swapFree=4180924/4192956
[pid=18774] ppid=18772 vsize=1368 CPUtime=0
/proc/18774/stat : 18774 (PBS4L) R 18772 18774 18728 0 -1 4194304 146 0 0 0 0 0 0 0 19 0 1 0 250743700 1400832 128 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 135140097 0 0 4096 0 0 0 0 17 1 0 0
/proc/18774/statm: 342 128 104 232 0 107 0

Child status: 0
Real time (s): 0.0178711
CPU time (s): 0.014996
CPU user time (s): 0.013997
CPU system time (s): 0.000999
CPU usage (%): 83.9122
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node61 on Fri Jun  9 10:59:18 UTC 2006


FILE ID= 48502-1149850758

PBS_JOBID= 383027

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/factor/normalized-factor-size=9-P=149-Q=167.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node61/48502-1149850758/instance-48502-1149850758.opb 349499124
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node61/watcher-48502-1149850758 -o ROOT/results/node61/solver-48502-1149850758 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node61/48502-1149850758/instance-48502-1149850758.opb 349499124

MD5SUM SOLVER= ab46593c31a6a47b9d9920387a00d332
MD5SUM BENCH=  1f78971d13423a3a94987e1d1496bfe5

RANDOM SEED= 349499124


/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:       1810248 kB
Buffers:         32532 kB
Cached:         142732 kB
SwapCached:       3780 kB
Active:          74052 kB
Inactive:       109972 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1810248 kB
SwapTotal:     4192956 kB
SwapFree:      4180924 kB
Dirty:             272 kB
Writeback:           0 kB
Mapped:          14728 kB
Slab:            47732 kB
Committed_AS:   527836 kB
PageTables:       1408 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node61 on Fri Jun  9 10:59:18 UTC 2006