Trace number 48251

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
bsolo 2006/05OPT79 1.10183 1.11063

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/
factor/normalized-factor-size=9-P=79-Q=331.opb
MD5SUMedf15b432615a3e971e6c5718d9addbd
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark79
Best CPU time to get the best result obtained on this benchmark0.007997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 79
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 65536
Number of bits of the biggest number in a constraint 17
Biggest sum of numbers in a constraint 287270
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

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 Time Limit set via PBTIMEOUT to 1800
0.01	c INFO: OSL Context initialized.
0.02	c Initial problem consists of 99 variables and 245 constraints.
0.02	c No problem reductions applied in OPT. instance.
0.02	c	preprocess terminated. Elapsed time: 0.016
0.02	c After prepocess the problem consists of 96 variables and 239 constraints.
0.02	c Initial Lower Bound: 0
0.03	c Restart #1 #Var: 96 LB: 0 @ 0.03
0.06	c Restart #2 #Var: 96 LB: 0 @ 0.058
0.11	c Restart #3 #Var: 96 LB: 0 @ 0.107
0.20	c Restart #4 #Var: 96 LB: 0 @ 0.193
0.34	c Restart #5 #Var: 96 LB: 0 @ 0.336
0.58	c Restart #6 #Var: 96 LB: 0 @ 0.578
0.94	c Restart #7 #Var: 96 LB: 0 @ 0.933
0.95	c Sol. found (all assignments made)...
0.95	o 331
0.95	c NEW SOLUTION FOUND: 331 @ 0.949
0.98	c Sol. found (all assignments made)...
0.98	o 79
0.98	c NEW SOLUTION FOUND: 79 @ 0.976
1.10	s OPTIMUM FOUND
1.10	c Cost: 79
1.10	v x1 x2 x3 x4 -x5 -x6 x7 -x8 -x9 x19 x10 x20 x11 -x21 -x12 x22 x13 -x23 -x14 -x24 -x15 x25 x16 -x26 -x17 x27 x18 x28 x29 -x30 x31 -x32
1.10	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
1.10	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
1.10	v -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99
1.10	c Exit Code: 30
1.10	c Total time: 1.099 s

Verifier Data (download as text)

OK	79

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/node75/watcher-48251-1149843647 -o ROOT/results/node75/solver-48251-1149843647 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node75/48251-1149843647/instance-48251-1149843647.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.99 0.99 0.91 2/64 7048
/proc/meminfo: memFree=1396120/2055920 swapFree=4182500/4192956
[pid=7048] ppid=7046 vsize=2900 CPUtime=0
/proc/7048/stat : 7048 (bsolo) R 7046 7048 7002 0 -1 0 43 0 0 0 0 0 0 0 18 0 1 0 250028120 2969600 27 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 6734123 0 0 4096 0 0 0 0 17 1 0 0
/proc/7048/statm: 725 27 19 55 0 38 0

Child status: 30
Real time (s): 1.11063
CPU time (s): 1.10183
CPU user time (s): 1.08483
CPU system time (s): 0.016997
CPU usage (%): 99.2078
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node75 on Fri Jun  9 09:00:47 UTC 2006


FILE ID= 48251-1149843647

PBS_JOBID= 382260

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/factor/normalized-factor-size=9-P=79-Q=331.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node75/48251-1149843647/instance-48251-1149843647.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node75/watcher-48251-1149843647 -o ROOT/results/node75/solver-48251-1149843647 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node75/48251-1149843647/instance-48251-1149843647.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  edf15b432615a3e971e6c5718d9addbd

RANDOM SEED= 62665058


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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1396328 kB
Buffers:         42844 kB
Cached:         539376 kB
SwapCached:       2240 kB
Active:         140044 kB
Inactive:       450932 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1396328 kB
SwapTotal:     4192956 kB
SwapFree:      4182500 kB
Dirty:             268 kB
Writeback:           0 kB
Mapped:          16044 kB
Slab:            54576 kB
Committed_AS:   525016 kB
PageTables:       1448 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node75 on Fri Jun  9 09:00:48 UTC 2006