Trace number 85343

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
glpPB 0.2OPT50 14.7238 14.7317

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-50-2_0-yes1-3.opb
MD5SUMe0fa076a6939280b8b7e6d5e10f6c17b
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark50
Best CPU time to get the best result obtained on this benchmark0.004998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 50
Optimality of the best value was proved YES
Number of variables100
Total number of constraints150
Number of constraints which are clauses150
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 constraint2
Maximum length of a constraint3
Number of terms in the objective function 100
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 100
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 100
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

Solver Data (download as text)

0.00	c glpPB 0.2 (July 2006)
0.00	c An Application of GLPK 4.10 for PB Constraints
0.00	c Done @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
14.73	c starting to Solve
14.73	c total time = 14.72
14.73	o 50
14.73	c quality of integer solution is H
14.73	s OPTIMUM FOUND
14.73	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 x31 -x32
14.73	v -x33 x34 x35 -x36 -x37 x38 -x39 x40 x41 -x42 -x43 x44 x45 -x46 x47 -x48 -x49 x50 x51 -x52 x53 -x54 -x55 x56 -x57 x58 -x59 x60 -x61
14.73	v x62 x63 -x64 -x65 x66 x67 -x68 x69 -x70 x71 -x72 -x73 x74 x75 -x76 -x77 x78 x79 -x80 -x81 x82 x83 -x84 x85 -x86 x87 -x88 -x89 x90
14.73	v x91 -x92 x93 -x94 -x95 x96 x97 -x98 -x99 x100

Verifier Data (download as text)

OK	50

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

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

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node30/watcher-85343-1154169585 -o ROOT/results/node30/solver-85343-1154169585 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node30/85343-1154169585/instance-85343-1154169585.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.99 0.97 0.91 2/64 1734
/proc/meminfo: memFree=1404192/2055920 swapFree=4178648/4192956
[pid=1734] ppid=1732 vsize=2376 CPUtime=0
/proc/1734/stat : 1734 (glpPBv3) R 1732 1734 1681 0 -1 0 198 0 0 0 0 0 0 0 18 0 1 0 163818367 2433024 168 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 4160275024 0 0 4096 0 0 0 0 17 1 0 0
/proc/1734/statm: 594 177 155 40 0 11 0

[startup+10.0019 s]
/proc/loadavg: 0.99 0.97 0.91 2/64 1734
/proc/meminfo: memFree=1403616/2055920 swapFree=4178648/4192956
[pid=1734] ppid=1732 vsize=2932 CPUtime=9.99
/proc/1734/stat : 1734 (glpPBv3) R 1732 1734 1681 0 -1 0 381 0 0 0 991 8 0 0 25 0 1 0 163818367 3002368 350 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/1734/statm: 733 350 227 40 0 150 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 2932

Child status: 30
Real time (s): 14.7317
CPU time (s): 14.7238
CPU user time (s): 14.5878
CPU system time (s): 0.135979
CPU usage (%): 99.9461
Max. virtual memory (cumulated for all children) (Kb): 2932
The end

Launcher Data (download as text)

Begin job on node30 on Sat Jul 29 10:39:45 UTC 2006


FILE ID= 85343-1154169585

PBS_JOBID= 893117

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-50-2_0-yes1-3.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node30/85343-1154169585/instance-85343-1154169585.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node30/watcher-85343-1154169585 -o ROOT/results/node30/solver-85343-1154169585 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node30/85343-1154169585/instance-85343-1154169585.opb

MD5SUM SOLVER= 29ce95346658d7502ba983059bfb8cff
MD5SUM BENCH=  e0fa076a6939280b8b7e6d5e10f6c17b

RANDOM SEED= 159237490

TIMEOUT= 1800 seconds


/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.256
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.256
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:       1404400 kB
Buffers:         36392 kB
Cached:         534152 kB
SwapCached:       8000 kB
Active:         111496 kB
Inactive:       471912 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1404400 kB
SwapTotal:     4192956 kB
SwapFree:      4178648 kB
Dirty:             208 kB
Writeback:           0 kB
Mapped:          14496 kB
Slab:            54164 kB
Committed_AS:   699804 kB
PageTables:       1392 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node30 on Sat Jul 29 10:40:00 UTC 2006