Trace number 35229

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
minisat+ 1.14OPT18 0.439933 0.443982

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/mps-v2-20-10/MIPLIB/
miplib/normalized-mps-v2-20-10-stein27.opb
MD5SUMad4e33c2a351634ad3ada1c06c0b1126
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark18
Best CPU time to get the best result obtained on this benchmark0.279956
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 18
Optimality of the best value was proved YES
Number of variables27
Total number of constraints118
Number of constraints which are clauses117
Number of constraints which are cardinality constraints (but not clauses)1
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint3
Maximum length of a constraint27
Number of terms in the objective function 27
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 27
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 13
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 40
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 Parsing PB file...
0.00	c Converting 118 PB-constraints to clauses...
0.00	c   -- Unit propagations: (none)
0.00	c   -- Detecting intervals from adjacent constraints: (none)
0.00	c   -- Clauses(.)/Splits(s): .....................................................................................................................
0.00	c ---[   0]---> Sorter-cost:  312     Base:
0.00	c ==================================[MINISAT+]==================================
0.00	c | Conflicts | Original         | Learnt                           | Progress |
0.00	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.00	c ==============================================================================
0.00	c |         0 |     430     1090 |     143       0        0     nan |  0.000 % |
0.00	c ==============================================================================
0.00	c Found solution: 21
0.00	o 21
0.00	c ---[   0]---> Sorter-cost:  146     Base:
0.01	c ==================================[MINISAT+]==================================
0.01	c | Conflicts | Original         | Learnt                           | Progress |
0.01	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.01	c ==============================================================================
0.01	c |         0 |     720     1779 |     240       0        0     nan |  0.000 % |
0.01	c ==============================================================================
0.01	c Found solution: 18
0.01	o 18
0.01	c ---[   0]---> Sorter-cost:    0     Base:
0.01	c ==================================[MINISAT+]==================================
0.01	c | Conflicts | Original         | Learnt                           | Progress |
0.01	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.01	c ==============================================================================
0.01	c |         6 |     744     1845 |     248       5       23     4.6 |  0.000 % |
0.01	c |       106 |     744     1845 |     272     105     1251    11.9 |  4.430 % |
0.02	c |       256 |     722     1795 |     300     253     2624    10.4 |  6.471 % |
0.02	c |       481 |     708     1763 |     330     298     2929     9.8 |  7.830 % |
0.04	c |       819 |     708     1763 |     363     240     2046     8.5 |  7.831 % |
0.06	c |      1325 |     708     1763 |     399     294     2601     8.8 |  7.830 % |
0.09	c |      2084 |     708     1763 |     439     278     2325     8.4 |  7.833 % |
0.13	c |      3223 |     708     1763 |     483     386     2870     7.4 |  7.850 % |
0.20	c |      4931 |     685     1701 |     531     516     4612     8.9 |  8.845 % |
0.29	c |      7493 |     634     1576 |     584     347     2714     7.8 | 13.267 % |
0.44	c |     11337 |     312      774 |     643     115      784     6.8 | 44.262 % |
0.44	c ==============================================================================
0.44	c Optimal solution: 18
0.44	s OPTIMUM FOUND
0.44	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
0.44	c _______________________________________________________________________________
0.44	c 
0.44	c restarts              : 13
0.44	c conflicts             : 11343          (25783 /sec)
0.44	c decisions             : 12904          (29332 /sec)
0.44	c propagations          : 0              (0 /sec)
0.44	c inspects              : 0              (0 /sec)
0.44	c CPU time              : 0.439933 s
0.44	c _______________________________________________________________________________

Verifier Data (download as text)

OK	18

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/node84/watcher-35229-1149368784 -o ROOT/results/node84/solver-35229-1149368784 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/35229-1149368784/instance-35229-1149368784.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.97 2/67 27940
/proc/meminfo: memFree=1575704/2055892 swapFree=4085292/4096564
[pid=27940] ppid=27938 vsize=1048 CPUtime=0
/proc/27940/stat : 27940 (minisat+) R 27938 27940 27894 0 -1 4194304 106 0 0 0 0 0 0 0 19 0 1 0 202517701 1073152 92 18446744073709551615 134512640 135395479 4294956672 18446744073709551615 134629197 0 0 4096 16386 0 0 0 17 1 0 0
/proc/27940/statm: 262 92 74 215 0 44 0

Child status: 30
Real time (s): 0.443982
CPU time (s): 0.439933
CPU user time (s): 0.439933
CPU system time (s): 0
CPU usage (%): 99.088
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node84 on Sat Jun  3 21:06:24 UTC 2006


FILE ID= 35229-1149368784

PBS_JOBID= 312024

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/mps-v2-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-stein27.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/35229-1149368784/instance-35229-1149368784.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node84/watcher-35229-1149368784 -o ROOT/results/node84/solver-35229-1149368784 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/35229-1149368784/instance-35229-1149368784.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  ad4e33c2a351634ad3ada1c06c0b1126

RANDOM SEED= 610689250


/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.231
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.15
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.231
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.43
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1575912 kB
Buffers:         34928 kB
Cached:         379016 kB
SwapCached:       2420 kB
Active:          59680 kB
Inactive:       362848 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1575912 kB
SwapTotal:     4096564 kB
SwapFree:      4085292 kB
Dirty:             168 kB
Writeback:           0 kB
Mapped:          16424 kB
Slab:            44200 kB
Committed_AS:   413368 kB
PageTables:       1272 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node84 on Sat Jun  3 21:06:25 UTC 2006