Trace number 50410

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.021029

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=220-sizeP=111-sizeQ=220-229130880.opb
MD5SUM20fad26c16d154a41eda0484a6e6eae7
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark1
Best CPU time to get the best result obtained on this benchmark42.1306
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 1
Optimality of the best value was proved YES
Number of variables24751
Total number of constraints73261
Number of constraints which are clauses73260
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 constraint24420
Number of terms in the objective function 111
Biggest coefficient in the objective function 1298074214633706907132624082305024
Number of bits for the biggest coefficient in the objective function 111
Sum of the numbers in the objective function 2596148429267413814265248164610047
Number of bits of the sum of numbers in the objective function 111
Biggest number in a constraint 1093625362391505962186251113558810682676584715446606218212885303204976499599687961611756588511526912
Number of bits of the biggest number in a constraint 330
Biggest sum of numbers in a constraint 4374501449566023848745004454235242451901741326209966194279906655789612083583747144123545843134987905
Number of bits of the biggest sum of numbers331
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.01	c INFO: OSL Context initialized.
0.01	c BIG Int formula...
0.01	c Integer values too big to handle...
0.01	c Parse Error 8
0.01	c Problem opening input file name: ROOT/tmp/node84/50410-1149921057/instance-50410-1149921057.opb
0.01	s UNKNOWN
0.01	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/node84/watcher-50410-1149921057 -o ROOT/results/node84/solver-50410-1149921057 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node84/50410-1149921057/instance-50410-1149921057.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.60 0.88 0.88 2/67 21724
/proc/meminfo: memFree=1347688/2055892 swapFree=4085312/4096564
[pid=21724] ppid=21722 vsize=4672 CPUtime=0
/proc/21724/stat : 21724 (bsolo) R 21722 21724 21678 0 -1 0 155 0 0 0 0 0 0 0 18 0 1 0 257745000 4784128 136 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 8076184 0 0 4096 0 0 0 0 17 1 0 0
/proc/21724/statm: 1168 142 108 55 0 46 0

Child status: 0
Real time (s): 0.021029
CPU time (s): 0.011997
CPU user time (s): 0.003999
CPU system time (s): 0.007998
CPU usage (%): 57.0498
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node84 on Sat Jun 10 06:30:57 UTC 2006


FILE ID= 50410-1149921057

PBS_JOBID= 386149

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=220-sizeP=111-sizeQ=220-229130880.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node84/50410-1149921057/instance-50410-1149921057.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node84/watcher-50410-1149921057 -o ROOT/results/node84/solver-50410-1149921057 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node84/50410-1149921057/instance-50410-1149921057.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  20fad26c16d154a41eda0484a6e6eae7

RANDOM SEED= 180771903


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


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1347896 kB
Buffers:         45100 kB
Cached:         585656 kB
SwapCached:       2460 kB
Active:         150696 kB
Inactive:       488756 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1347896 kB
SwapTotal:     4096564 kB
SwapFree:      4085312 kB
Dirty:             180 kB
Writeback:           0 kB
Mapped:          16436 kB
Slab:            55208 kB
Committed_AS:   714156 kB
PageTables:       1272 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node84 on Sat Jun 10 06:30:57 UTC 2006