Trace number 50416

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/05? 0.011997 0.045762

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=320-sizeP=161-sizeQ=320-420453220-max.opb
MD5SUM731d8a8b62f1165d7f7ff2eb0e8bed96
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmark
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables52001
Total number of constraints154561
Number of constraints which are clauses154560
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 constraint51520
Number of terms in the objective function 161
Biggest coefficient in the objective function 1461501637330902918203684832716283019655932542976
Number of bits for the biggest coefficient in the objective function 161
Sum of the numbers in the objective function 2923003274661805836407369665432566039311865085951
Number of bits of the sum of numbers in the objective function 161
Biggest number in a constraint 1560874275157996115690798614896583152874299071332485575429578479812685869409882810060153051531745985579913465560703311447723987839644142653145088
Number of bits of the biggest number in a constraint 480
Biggest sum of numbers in a constraint 6243497100631984462763194459586332611497196285329458171408770520629035540670020835398097850925707779467176054569131054629458594384801759081011045
Number of bits of the biggest sum of numbers481
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 Time Limit set via PBTIMEOUT to 1800
0.04	c INFO: OSL Context initialized.
0.04	c Integer values too big to handle...
0.04	c Parse Error 8
0.04	c Problem opening input file name: ROOT/tmp/node76/50416-1149921105/instance-50416-1149921105.opb
0.04	s UNKNOWN
0.04	c Exit Code: 0

Verifier Data (download as text)

ERROR: no interpretation found !

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.47 0.85 0.87 2/68 25634
/proc/meminfo: memFree=1761816/2055888 swapFree=4085384/4096564
[pid=25634] ppid=25632 vsize=3228 CPUtime=0
/proc/25634/stat : 25634 (bsolo) R 25632 25634 25588 0 -1 0 54 0 0 0 0 0 0 0 18 0 1 0 257749969 3305472 38 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4817844 0 0 4096 0 0 0 0 17 1 0 0
/proc/25634/statm: 807 38 28 55 0 40 0

Child status: 0
Real time (s): 0.045762
CPU time (s): 0.011997
CPU user time (s): 0.006998
CPU system time (s): 0.004999
CPU usage (%): 26.2161
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node76 on Sat Jun 10 06:31:46 UTC 2006


FILE ID= 50416-1149921105

PBS_JOBID= 386173

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=320-sizeP=161-sizeQ=320-420453220-max.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node76/50416-1149921105/instance-50416-1149921105.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-50416-1149921105 -o ROOT/results/node76/solver-50416-1149921105 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node76/50416-1149921105/instance-50416-1149921105.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  731d8a8b62f1165d7f7ff2eb0e8bed96

RANDOM SEED= 522931504


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


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1762088 kB
Buffers:         30332 kB
Cached:         191704 kB
SwapCached:       2364 kB
Active:          78136 kB
Inactive:       152588 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1762088 kB
SwapTotal:     4096564 kB
SwapFree:      4085384 kB
Dirty:             116 kB
Writeback:           0 kB
Mapped:          16564 kB
Slab:            49588 kB
Committed_AS:   651232 kB
PageTables:       1264 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node76 on Sat Jun 10 06:31:46 UTC 2006