Trace number 37957

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.3OPT8276 0.178971 0.220928

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/ttp/normalized-data4_3.opb
MD5SUM12a5969fc5fa7320821e43a146878312
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark8276
Best CPU time to get the best result obtained on this benchmark0.178971
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 8276
Optimality of the best value was proved YES
Number of variables144
Total number of constraints704
Number of constraints which are clauses464
Number of constraints which are cardinality constraints (but not clauses)96
Number of constraints which are nor clauses,nor cardinality constraints144
Minimum length of a constraint2
Maximum length of a constraint12
Number of terms in the objective function 48
Biggest coefficient in the objective function 929
Number of bits for the biggest coefficient in the objective function 10
Sum of the numbers in the objective function 25088
Number of bits of the sum of numbers in the objective function 15
Biggest number in a constraint 929
Number of bits of the biggest number in a constraint 10
Biggest sum of numbers in a constraint 25088
Number of bits of the biggest sum of numbers15
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.01	c Pueblo version 1.4 (September 2005)
0.01	c Developed @ University of Michigan, Ann Arbor, MI
0.01	c  by Hossein Sheini
0.02	c starting to Solve
0.02	c #variables read: 144 - #constraints read: 765
0.02	o 8413
0.02	o 8290
0.02	o 8276
0.18	c optimum objective found = 8276
0.18	c total time              : 0.17 s
0.18	s OPTIMUM FOUND
0.18	v -x97 -x98 x99 -x100 x101 -x102 x103 -x104 -x105 -x106 x107 -x108 -x109 -x110 x111 -x112 x113 -x114 x115 -x116 -x117 -x118 x119
0.18	v -x120 -x121 x122 -x123 -x124 -x125 x126 x127 x128 -x129 -x130 -x131 x132 -x133 x134 -x135 x136 -x137 -x138 -x139 -x140 x141
0.18	v -x142 x143 -x144 -x2 x18 -x34 -x50 -x66 -x82 -x3 -x19 x35 -x51 -x67 -x83 x4 -x20 -x36 -x52 -x68 -x84 -x5 -x21 -x37 -x53 x69 -x85
0.18	v -x7 -x23 -x39 x55 -x71 -x87 -x8 -x24 -x40 -x56 -x72 x88 -x9 -x25 -x41 -x57 -x73 x89 x10 -x26 -x42 -x58 -x74 -x90 -x12 x28 -x44 -x60
0.18	v -x76 -x92 -x13 -x29 -x45 x61 -x77 -x93 -x14 -x30 x46 -x62 -x78 -x94 -x15 -x31 -x47 -x63 x79 -x95 x6 x22 x38 -x54 -x70 -x86 -x11
0.18	v -x27 x43 x59 x75 -x91 x16 x32 -x48 -x64 -x80 x96 -x1 -x17 -x33 x49 x65 x81

Verifier Data (download as text)

OK	8276

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.98 2/64 22184
/proc/meminfo: memFree=1869640/2055920 swapFree=4181408/4192956
[pid=22184] ppid=22182 vsize=172 CPUtime=0
/proc/22184/stat : 22184 (Pueblo13) D 22182 22184 22138 0 -1 4194304 38 0 0 0 0 0 0 0 19 0 1 0 205670885 176128 23 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 2515748 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/22184/statm: 43 23 18 16 0 2 0

Child status: 30
Real time (s): 0.220928
CPU time (s): 0.178971
CPU user time (s): 0.171973
CPU system time (s): 0.006998
CPU usage (%): 81.0087
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node49 on Sun Jun  4 05:47:17 UTC 2006


FILE ID= 37957-1149400037

PBS_JOBID= 313943

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/ttp/normalized-data4_3.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node49/37957-1149400037/instance-37957-1149400037.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node49/watcher-37957-1149400037 -o ROOT/results/node49/solver-37957-1149400037 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node49/37957-1149400037/instance-37957-1149400037.opb

MD5SUM SOLVER= b45add8200bccdf53727749bff226bd1
MD5SUM BENCH=  12a5969fc5fa7320821e43a146878312

RANDOM SEED= 768609829


/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.216
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.216
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:       1869848 kB
Buffers:          9824 kB
Cached:         116384 kB
SwapCached:       3264 kB
Active:          21776 kB
Inactive:       113216 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1869848 kB
SwapTotal:     4192956 kB
SwapFree:      4181408 kB
Dirty:             164 kB
Writeback:           0 kB
Mapped:          14844 kB
Slab:            37016 kB
Committed_AS:   396328 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 node49 on Sun Jun  4 05:47:18 UTC 2006