Trace number 45770

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
PB-smodels 1.31OPT50 0.056991 0.0544789

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-50-1_6-yes1-4.opb
MD5SUM3ecbbaec590cb5aaef80ac852b87b8ad
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.002998
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 constraints130
Number of constraints which are clauses128
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints2
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 2
Number of bits of the biggest number in a constraint 2
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 Running pbsmodels-v1.31
0.04	o 50
0.05	s OPTIMUM FOUND
0.05	v x2 x3 x6 x8 x10 x11 x14 x16 x18 x19 x21 x24 x26 x27 x29 x31 x34 x35 x37 x39 x42 x43 x45 x47 x49 x52 x54 x56 x58 x60 x62 x63 x66 x68 x69
0.05	v x71 x74 x76 x77 x79 x82 x83 x85 x87 x90 x91 x93 x96 x98 x99 -x1 -x4 -x5 -x7 -x9 -x12 -x13 -x15 -x17 -x20 -x22 -x23 -x25 -x28 -x30 -x32
0.05	v -x33 -x36 -x38 -x40 -x41 -x44 -x46 -x48 -x50 -x51 -x53 -x55 -x57 -x59 -x61 -x64 -x65 -x67 -x70 -x72 -x73 -x75 -x78 -x80 -x81 -x84
0.05	v -x86 -x88 -x89 -x92 -x94 -x95 -x97 -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.1 (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/node69/watcher-45770-1149652946 -o ROOT/results/node69/solver-45770-1149652946 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node69/45770-1149652946/instance-45770-1149652946.opb 260614014 ROOT/tmp/node69/45770-1149652946 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.74 0.91 0.90 2/64 19833
/proc/meminfo: memFree=1732996/2055920 swapFree=4182212/4192956
[pid=19833] ppid=19831 vsize=5360 CPUtime=0
/proc/19833/stat : 19833 (runpbsmodels) R 19831 19833 19787 0 -1 4194304 266 0 0 0 0 0 0 0 19 0 1 0 230964623 5488640 233 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 237947644575 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/19833/statm: 1340 233 194 169 0 51 0
[pid=19834] ppid=19833 vsize=5360 CPUtime=0
/proc/19834/stat : 19834 (runpbsmodels) R 19833 19833 19787 0 -1 4194368 13 0 0 0 0 0 0 0 19 0 1 0 230964624 5488640 234 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 4401232 0 0 4100 65536 0 0 0 17 1 0 0
/proc/19834/statm: 1340 234 195 169 0 51 0

Child status: 0
Real time (s): 0.0544789
CPU time (s): 0.056991
CPU user time (s): 0.037994
CPU system time (s): 0.018997
CPU usage (%): 104.611
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node69 on Wed Jun  7 04:02:26 UTC 2006


FILE ID= 45770-1149652946

PBS_JOBID= 324269

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-50-1_6-yes1-4.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node69/45770-1149652946/instance-45770-1149652946.opb 260614014  ROOT/tmp/node69/45770-1149652946
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node69/watcher-45770-1149652946 -o ROOT/results/node69/solver-45770-1149652946 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node69/45770-1149652946/instance-45770-1149652946.opb 260614014  ROOT/tmp/node69/45770-1149652946

MD5SUM SOLVER= 95562bc622ddb1f976359072aec5ad24 7fcd858753252b26b88f3383e979819a c732bc4c3aeda9195daa74a308a1f78e b7e54d975d35ab28450b6de5c14d303e f7da3270b2cd5190fa0cd9af9b854ca4
MD5SUM BENCH=  3ecbbaec590cb5aaef80ac852b87b8ad

RANDOM SEED= 260614014


/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.232
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.232
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:       1733268 kB
Buffers:         29804 kB
Cached:         227544 kB
SwapCached:       2548 kB
Active:          82508 kB
Inactive:       183656 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1733268 kB
SwapTotal:     4192956 kB
SwapFree:      4182212 kB
Dirty:             268 kB
Writeback:           0 kB
Mapped:          15424 kB
Slab:            42456 kB
Committed_AS:   461792 kB
PageTables:       1496 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node69 on Wed Jun  7 04:02:26 UTC 2006