Trace number 459257

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
PBS4_v2 2007-03-23OPT33 0.024996 0.02653

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-LIN/submittedPB07/aksoy/
area_partials/normalized-fir07_area_partials.opb
MD5SUM7ce2ce9765bc91d2f0a2aa267ffcb923
Bench CategoryOPT-SMALLINT-LIN (optimisation, small integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark33
Best CPU time to get the best result obtained on this benchmark0.013997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 33
Optimality of the best value was proved YES
Number of variables190
Total number of constraints419
Number of constraints which are clauses419
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 constraint1
Maximum length of a constraint30
Number of terms in the objective function 92
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 92
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 92
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/0.00	c PBS v4 by Bashar Al-Rawi & Fadi Aloul
0.00/0.00	c Solving /tmp/evaluation/459257-1178652748/instance-459257-1178652748.opb ......
0.00/0.00	c done parsing opb.
0.00/0.00	o 55
0.00/0.00	o 54
0.00/0.00	o 53
0.00/0.00	o 52
0.00/0.00	o 51
0.00/0.00	o 50
0.00/0.00	o 49
0.00/0.00	o 48
0.00/0.00	o 47
0.00/0.00	o 46
0.00/0.00	o 45
0.00/0.00	o 44
0.00/0.00	o 43
0.00/0.00	o 42
0.00/0.00	o 41
0.00/0.00	o 40
0.00/0.00	o 39
0.00/0.00	o 38
0.00/0.00	o 37
0.00/0.00	o 36
0.00/0.01	o 35
0.00/0.01	o 34
0.00/0.01	o 33
0.00/0.02	o 33
0.00/0.02	s OPTIMUM FOUND
0.00/0.02	c Total Run Time					0.020997
0.00/0.02	v x1 x10 -x100 -x101 -x102 -x103 -x104 -x105 -x106 -x107 -x108 -x109 x11 -x110 -x111 -x112 -x113 -x114 -x115 -x116 x117 -x118
0.00/0.02	v -x119 x12 -x120 -x121 -x122 -x123 -x124 -x125 x126 -x127 -x128 -x129 x13 -x130 -x131 -x132 -x133 -x134 -x135 -x136 -x137 -x138
0.00/0.02	v -x139 x14 x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 -x148 -x149 x15 -x150 -x151 -x152 -x153 -x154 -x155 x156 x157 x158
0.00/0.02	v -x159 x16 -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167 -x168 -x169 x17 -x170 -x171 -x172 -x173 -x174 -x175 x176 -x177 -x178
0.00/0.02	v -x179 x18 -x180 -x181 -x182 -x183 -x184 -x185 -x186 -x187 -x188 -x189 -x19 -x190 x2 -x20 -x21 -x22 -x23 -x24 -x25 -x26 -x27
0.00/0.02	v -x28 -x29 x3 -x30 -x31 x32 x33 -x34 -x35 -x36 -x37 -x38 -x39 x4 -x40 x41 x42 x43 x44 -x45 -x46 -x47 -x48 -x49 x5 -x50 -x51 x52 x53
0.00/0.02	v x54 x55 x56 x57 -x58 -x59 -x6 -x60 -x61 -x62 -x63 -x64 x65 -x66 -x67 -x68 x69 x7 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79
0.00/0.02	v x8 -x80 -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 x9 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99

Verifier Data (download as text)

OK	33

Conversion Script Data (download as text)

/tmp/evaluation/459257-1178652748/instance-459257-1178652748.opb is already a linear file

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node76/watcher-459257-1178652748 -o ROOT/results/node76/solver-459257-1178652748 -C 1800 -W 3600 -M 1800 --output-limit 1,15 PBS4_SAT07v2 /tmp/evaluation/459257-1178652748/instance-459257-1178652748.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.91 0.95 0.98 3/69 18651
/proc/meminfo: memFree=1896848/2055888 swapFree=4087224/4096564
[pid=18651] ppid=18649 vsize=1320 CPUtime=0
/proc/18651/stat : 18651 (PBS4_SAT07v2) R 18649 18651 18404 0 -1 4194304 150 0 0 0 0 0 0 0 19 0 1 0 313189320 1351680 133 18446744073709551615 134512640 135410602 4294956704 18446744073709551615 135059409 0 0 4096 16384 0 0 0 17 1 0 0
/proc/18651/statm: 330 133 101 219 0 107 0

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

Child status: 0
Real time (s): 0.02653
CPU time (s): 0.024996
CPU user time (s): 0.024996
CPU system time (s): 0
CPU usage (%): 94.2178
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.024996
system time used= 0
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 188
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= 8
involuntary context switches= 0

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node76 on Tue May  8 19:32:28 UTC 2007

IDJOB= 459257
IDBENCH= 25028
IDSOLVER= 200
FILE ID= node76/459257-1178652748

PBS_JOBID= 5218404

Free space on /tmp= 66649 MiB

SOLVER NAME= PBS4_v2 2007-03-23
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-LIN/submittedPB07/aksoy/area_partials/normalized-fir07_area_partials.opb
COMMAND LINE= PBS4_SAT07v2 /tmp/evaluation/459257-1178652748/instance-459257-1178652748.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node76/convwatcher-459257-1178652748 -o ROOT/results/node76/conversion-459257-1178652748 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/459257-1178652748/instance-459257-1178652748.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-459257-1178652748 -o ROOT/results/node76/solver-459257-1178652748 -C 1800 -W 3600 -M 1800 --output-limit 1,15  PBS4_SAT07v2 /tmp/evaluation/459257-1178652748/instance-459257-1178652748.opb

META MD5SUM SOLVER= 18cd8c68a4d3bfb01f29079966475a33
MD5SUM BENCH=  7ce2ce9765bc91d2f0a2aa267ffcb923

RANDOM SEED= 420759201

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node76.alineos.net 2.6.9-34.ELsmp #1 SMP Thu Mar 9 06:23:23 GMT 2006 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.277
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	: 6006.17
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.277
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1897192 kB
Buffers:          6788 kB
Cached:          72144 kB
SwapCached:       2668 kB
Active:          79208 kB
Inactive:        10296 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1897192 kB
SwapTotal:     4096564 kB
SwapFree:      4087224 kB
Dirty:            2392 kB
Writeback:           0 kB
Mapped:          16792 kB
Slab:            55560 kB
Committed_AS:  5769664 kB
PageTables:       1424 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66649 MiB

End job on node76 on Tue May  8 19:32:28 UTC 2007