Trace number 38164

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.3OPT12 25.0202 25.0326

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
sorensson/garden/normalized-g7x7.opb
MD5SUMcb84e2b94add4387530e3674f52279cd
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark12
Best CPU time to get the best result obtained on this benchmark0.012997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 12
Optimality of the best value was proved YES
Number of variables49
Total number of constraints49
Number of constraints which are clauses49
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 constraint3
Maximum length of a constraint5
Number of terms in the objective function 49
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 49
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 49
Number of bits of the biggest sum of numbers6
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.00	c starting to Solve
0.00	c #variables read: 49 - #constraints read: 50
0.00	o 17
0.00	o 16
0.00	o 15
0.01	o 14
0.03	o 13
0.46	o 12
25.03	c optimum objective found = 12
25.03	c total time              : 25.02 s
25.03	s OPTIMUM FOUND
25.03	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
25.03	v -x31 x32 -x33 -x34 -x35 x36 -x37 -x38 -x39 -x40 -x41 x42 -x43 -x44 x45 -x46 x47 -x48 -x49

Verifier Data (download as text)

OK	12

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/node4/watcher-38164-1149287447 -o ROOT/results/node4/solver-38164-1149287447 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node4/38164-1149287447/instance-38164-1149287447.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.78 0.95 0.92 2/64 6776
/proc/meminfo: memFree=1800936/2055920 swapFree=4181448/4192956
[pid=6776] ppid=6774 vsize=172 CPUtime=0
/proc/6776/stat : 6776 (Pueblo13) D 6774 6776 6730 0 -1 4194304 38 0 0 0 0 0 0 0 19 0 1 0 194406570 176128 23 18446744073709551615 134512640 134579064 4294956688 18446744073709551615 10588964 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/6776/statm: 43 23 18 16 0 2 0

[startup+10.0018 s]
/proc/loadavg: 0.81 0.95 0.92 2/64 6776
/proc/meminfo: memFree=1800808/2055920 swapFree=4181448/4192956
[pid=6776] ppid=6774 vsize=2576 CPUtime=9.99
/proc/6776/stat : 6776 (Pueblo13) R 6774 6776 6730 0 -1 4194304 282 0 0 0 941 58 0 0 25 0 1 0 194406570 2637824 253 18446744073709551615 134512640 134579064 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/6776/statm: 644 253 205 16 0 85 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 2576

[startup+20.0078 s]
/proc/loadavg: 0.84 0.95 0.92 2/64 6776
/proc/meminfo: memFree=1800808/2055920 swapFree=4181448/4192956
[pid=6776] ppid=6774 vsize=2576 CPUtime=19.99
/proc/6776/stat : 6776 (Pueblo13) R 6774 6776 6730 0 -1 4194304 283 0 0 0 1885 114 0 0 25 0 1 0 194406570 2637824 254 18446744073709551615 134512640 134579064 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/6776/statm: 644 254 205 16 0 85 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 2576

Child status: 30
Real time (s): 25.0326
CPU time (s): 25.0202
CPU user time (s): 23.6084
CPU system time (s): 1.41179
CPU usage (%): 99.9503
Max. virtual memory (cumulated for all children) (Kb): 2576

Launcher Data (download as text)

Begin job on node4 on Fri Jun  2 22:30:47 UTC 2006


FILE ID= 38164-1149287447

PBS_JOBID= 306643

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/sorensson/garden/normalized-g7x7.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node4/38164-1149287447/instance-38164-1149287447.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-38164-1149287447 -o ROOT/results/node4/solver-38164-1149287447 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node4/38164-1149287447/instance-38164-1149287447.opb

MD5SUM SOLVER= b45add8200bccdf53727749bff226bd1
MD5SUM BENCH=  cb84e2b94add4387530e3674f52279cd

RANDOM SEED= 890833941


/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.236
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.236
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:       1801208 kB
Buffers:         20180 kB
Cached:         174504 kB
SwapCached:       3264 kB
Active:          45332 kB
Inactive:       158028 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1801208 kB
SwapTotal:     4192956 kB
SwapFree:      4181448 kB
Dirty:             184 kB
Writeback:           0 kB
Mapped:          14816 kB
Slab:            37312 kB
Committed_AS:   282180 kB
PageTables:       1500 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node4 on Fri Jun  2 22:31:12 UTC 2006