Trace number 47434

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.28OPT383 0.061989 0.057135

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/
factor/normalized-factor-size=9-P=383-Q=509.opb
MD5SUMab8ab255eb7e1089481372bc4abcd625
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark383
Best CPU time to get the best result obtained on this benchmark0.002999
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 383
Optimality of the best value was proved YES
Number of variables99
Total number of constraints244
Number of constraints which are clauses243
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint81
Number of terms in the objective function 9
Biggest coefficient in the objective function 256
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 511
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 194947
Number of bits of the biggest number in a constraint 18
Biggest sum of numbers in a constraint 456068
Number of bits of the biggest sum of numbers19
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.28
0.04	o 383
0.05	s OPTIMUM FOUND
0.05	v x1 x2 x3 x4 x5 x6 x7 x9 x19 x10 x21 x12 x22 x13 x23 x14 x24 x15 x25 x16 x26 x17 x27 x18 x28 x30 x31 x32 x33 x34 x35 x36 x37 x39 x40 x41 x42
0.05	v x43 x44 x45 x46 x48 x49 x50 x51 x52 x53 x54 x55 x57 x58 x59 x60 x61 x62 x63 x64 x66 x67 x68 x69 x70 x71 x72 x73 x75 x76 x77 x78 x79 x80
0.05	v x81 x91 x93 x94 x95 x96 x97 x98 x99 -x8 -x20 -x11 -x29 -x38 -x47 -x56 -x65 -x74 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x92

Verifier Data (download as text)

OK	383

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/node58/watcher-47434-1149859884 -o ROOT/results/node58/solver-47434-1149859884 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node58/47434-1149859884/instance-47434-1149859884.opb 482248013 ROOT/tmp/node58/47434-1149859884 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/64 27434
/proc/meminfo: memFree=1431640/2055920 swapFree=4191864/4192956
[pid=27434] ppid=27432 vsize=5360 CPUtime=0
/proc/27434/stat : 27434 (runpbsmodels) S 27432 27434 27388 0 -1 4194304 286 0 0 0 0 0 0 0 19 0 1 0 88035322 5488640 234 18446744073709551615 4194304 4889804 548682069168 18446744073709551615 226238194500 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/27434/statm: 1340 234 195 169 0 51 0
[pid=27435] ppid=27434 vsize=7504 CPUtime=0
/proc/27435/stat : 27435 (pbsmodels-v1.28) R 27434 27434 27388 0 -1 4194304 69 0 0 0 0 0 0 0 20 0 1 0 88035322 7684096 51 18446744073709551615 4194304 4206940 548682069008 18446744073709551615 226235577737 0 0 4096 0 0 0 0 17 1 0 0
/proc/27435/statm: 2135 52 39 3 0 55 0

Child status: 0
Real time (s): 0.057135
CPU time (s): 0.061989
CPU user time (s): 0.041993
CPU system time (s): 0.019996
CPU usage (%): 108.496
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node58 on Fri Jun  9 13:31:24 UTC 2006


FILE ID= 47434-1149859884

PBS_JOBID= 384108

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/factor/normalized-factor-size=9-P=383-Q=509.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node58/47434-1149859884/instance-47434-1149859884.opb 482248013  ROOT/tmp/node58/47434-1149859884
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node58/watcher-47434-1149859884 -o ROOT/results/node58/solver-47434-1149859884 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node58/47434-1149859884/instance-47434-1149859884.opb 482248013  ROOT/tmp/node58/47434-1149859884

MD5SUM SOLVER= f639f6b7f53e3afd14340f75c0e271ee 82c14a26114306e436bf36ef1d1c85a0 c893ceb51a2aaa4ab2f96d97b043cdf0 8c810dcfce02286b111d075d14837741 79b233270d136fcdcf9d8f80d20efef0
MD5SUM BENCH=  ab8ab255eb7e1089481372bc4abcd625

RANDOM SEED= 482248013


/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.276
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.276
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:       1431912 kB
Buffers:         42308 kB
Cached:         500912 kB
SwapCached:        576 kB
Active:          66688 kB
Inactive:       490708 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1431912 kB
SwapTotal:     4192956 kB
SwapFree:      4191864 kB
Dirty:             164 kB
Writeback:           0 kB
Mapped:          23008 kB
Slab:            52716 kB
Committed_AS:   480236 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 node58 on Fri Jun  9 13:31:24 UTC 2006