Trace number 430088

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.4OPT3 3.63445 3.63753

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=8-P0=257-P1=97-P2=149-B.opb
MD5SUM67e6ddc28ca754c7106cfc653b1e11ec
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3
Best CPU time to get the best result obtained on this benchmark0.048991
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3
Optimality of the best value was proved YES
Number of variables48
Total number of constraints5
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints5
Minimum length of a constraint8
Maximum length of a constraint80
Number of terms in the objective function 8
Biggest coefficient in the objective function 128
Number of bits for the biggest coefficient in the objective function 8
Sum of the numbers in the objective function 255
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 32768
Number of bits of the biggest number in a constraint 16
Biggest sum of numbers in a constraint 130560
Number of bits of the biggest sum of numbers17
Number of products (including duplicates)128
Sum of products size (including duplicates)256
Number of different products128
Sum of products size256

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/0.00	c Pueblo version 1.4 (September 2005)
0.00/0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00/0.00	c  by Hossein Sheini
0.00/0.00	c starting to Solve
0.00/0.00	c #variables read: 176 - #constraints read: 264
0.09/0.10	o 225
0.09/0.11	o 135
0.09/0.11	o 133
0.09/0.12	o 3
3.59/3.63	c optimum objective found = 3
3.59/3.63	c total time              : 3.63 s
3.59/3.63	s OPTIMUM FOUND
3.59/3.63	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 x49 x50 -x51 -x52 -x53 -x54 -x55
3.59/3.63	v -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80 -x81
3.59/3.63	v -x82 -x83 -x84 -x85 -x86 -x87 -x88 x89 x90 -x91 -x92 -x93 -x94 -x95 -x96 x97 x98 -x99 -x100 -x101 -x102 -x103 -x104 x105 x106
3.59/3.63	v -x107 -x108 -x109 -x110 -x111 -x112 x25 x26 -x27 -x28 -x29 x30 -x31 x32 -x33 x34 -x35 -x36 -x37 -x38 -x39 -x40 x113 x114 -x115
3.59/3.63	v -x116 -x117 x118 -x119 x120 x121 x122 -x123 -x124 -x125 x126 -x127 x128 x129 x130 -x131 -x132 -x133 x134 -x135 x136 -x137 -x138
3.59/3.63	v -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 -x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159
3.59/3.63	v -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167 -x168 -x169 -x170 -x171 -x172 -x173 -x174 -x175 -x176 -x41 -x42 x43 -x44 -x45
3.59/3.63	v -x46 -x47 -x48

Verifier Data (download as text)

OK	3

Conversion Script Data (download as text)

Linearizing /tmp/evaluation/430088-1177991708/instance-430088-1177991708.opb

Watcher Data (download as text)

runsolver version 3.2.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node47/watcher-430088-1177991708 -o ROOT/results/node47/solver-430088-1177991708 -C 1800 -W 3600 -M 1800 --output-limit 1,15 Pueblo /tmp/evaluation/430088-1177991708/instance-430088-1177991708.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.79 0.95 0.98 3/77 1034
/proc/meminfo: memFree=1813752/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2552 CPUtime=0
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 265 0 0 0 0 0 0 0 18 0 1 0 154016217 2613248 236 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 10985175 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 638 236 199 16 0 77 0

[startup+0.069063 s]
/proc/loadavg: 0.79 0.95 0.98 3/77 1034
/proc/meminfo: memFree=1813752/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2688 CPUtime=0.06
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 316 0 0 0 6 0 0 0 18 0 1 0 154016217 2752512 287 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 134517903 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 672 287 205 16 0 111 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 2688

[startup+0.101066 s]
/proc/loadavg: 0.79 0.95 0.98 3/77 1034
/proc/meminfo: memFree=1813752/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2688 CPUtime=0.09
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 316 0 0 0 9 0 0 0 18 0 1 0 154016217 2752512 287 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 10957773 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 672 287 205 16 0 111 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2688

[startup+0.301088 s]
/proc/loadavg: 0.79 0.95 0.98 3/77 1034
/proc/meminfo: memFree=1813752/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2816 CPUtime=0.29
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 332 0 0 0 29 0 0 0 19 0 1 0 154016217 2883584 303 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 704 303 205 16 0 143 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 2816

[startup+0.701131 s]
/proc/loadavg: 0.79 0.95 0.98 3/77 1034
/proc/meminfo: memFree=1813752/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2816 CPUtime=0.69
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 344 0 0 0 69 0 0 0 22 0 1 0 154016217 2883584 315 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 704 315 205 16 0 143 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 2816

[startup+1.50122 s]
/proc/loadavg: 0.79 0.95 0.98 2/78 1035
/proc/meminfo: memFree=1813232/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2816 CPUtime=1.49
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 353 0 0 0 148 1 0 0 25 0 1 0 154016217 2883584 324 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 704 324 205 16 0 143 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 2816

[startup+3.10139 s]
/proc/loadavg: 0.79 0.95 0.98 2/78 1035
/proc/meminfo: memFree=1813048/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2940 CPUtime=3.09
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 366 0 0 0 306 3 0 0 25 0 1 0 154016217 3010560 337 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 735 337 205 16 0 174 0
Current children cumulated CPU time (s) 3.09
Current children cumulated vsize (KiB) 2940

Solver just ended. Dumping a history of the last processes samples

[startup+3.50243 s]
/proc/loadavg: 0.79 0.95 0.98 2/78 1035
/proc/meminfo: memFree=1813048/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2940 CPUtime=3.49
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 367 0 0 0 346 3 0 0 25 0 1 0 154016217 3010560 338 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 735 338 205 16 0 174 0
Current children cumulated CPU time (s) 3.49
Current children cumulated vsize (KiB) 2940

[startup+3.60245 s]
/proc/loadavg: 0.79 0.95 0.98 2/78 1035
/proc/meminfo: memFree=1813048/2055920 swapFree=4157776/4192956
[pid=1034] ppid=1032 vsize=2940 CPUtime=3.59
/proc/1034/stat : 1034 (Pueblo) R 1032 1034 30166 0 -1 4194304 367 0 0 0 356 3 0 0 25 0 1 0 154016217 3010560 338 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/1034/statm: 735 338 205 16 0 174 0
Current children cumulated CPU time (s) 3.59
Current children cumulated vsize (KiB) 2940

Child status: 30
Real time (s): 3.63753
CPU time (s): 3.63445
CPU user time (s): 3.60045
CPU system time (s): 0.033994
CPU usage (%): 99.9151
Max. virtual memory (cumulated for all children) (KiB): 2944

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 3.60045
system time used= 0.033994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 373
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 13
involuntary context switches= 1

runsolver used 0.004999 second user time and 0.014997 second system time

The end

Launcher Data (download as text)

Begin job on node47 on Tue May  1 03:55:09 UTC 2007

IDJOB= 430088
IDBENCH= 47955
IDSOLVER= 165
FILE ID= node47/430088-1177991708

PBS_JOBID= 4728167

Free space on /tmp= 66562 MiB

SOLVER NAME= Pueblo 1.4
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=8-P0=257-P1=97-P2=149-B.opb
COMMAND LINE= Pueblo /tmp/evaluation/430088-1177991708/instance-430088-1177991708.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node47/convwatcher-430088-1177991708 -o ROOT/results/node47/conversion-430088-1177991708 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/430088-1177991708/instance-430088-1177991708.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node47/watcher-430088-1177991708 -o ROOT/results/node47/solver-430088-1177991708 -C 1800 -W 3600 -M 1800 --output-limit 1,15  Pueblo /tmp/evaluation/430088-1177991708/instance-430088-1177991708.opb

META MD5SUM SOLVER= 9ebec3e8d890fdeefad01654ad9b68b7
MD5SUM BENCH=  67e6ddc28ca754c7106cfc653b1e11ec

RANDOM SEED= 969133992

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node47.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.221
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.221
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:       1814160 kB
Buffers:         20964 kB
Cached:         138452 kB
SwapCached:       3444 kB
Active:          63380 kB
Inactive:       120176 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1814160 kB
SwapTotal:     4192956 kB
SwapFree:      4157776 kB
Dirty:            2452 kB
Writeback:           0 kB
Mapped:          31044 kB
Slab:            43688 kB
Committed_AS:  4097524 kB
PageTables:       1780 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66562 MiB

End job on node47 on Tue May  1 03:55:12 UTC 2007