Trace number 50417

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.005998 0.0205551

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=300-sizeP=151-sizeQ=300-692949159-max.opb
MD5SUM7e6b5d1bb2d5498810142d4e4cc2c6f4
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 variables45751
Total number of constraints135901
Number of constraints which are clauses135900
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 constraint45300
Number of terms in the objective function 151
Biggest coefficient in the objective function 1427247692705959881058285969449495136382746624
Number of bits for the biggest coefficient in the objective function 151
Sum of the numbers in the objective function 2854495385411919762116571938898990272765493247
Number of bits of the sum of numbers in the objective function 151
Biggest number in a constraint 1453677448591213781098647615776009068707282721374636120562980398361278576226795846652382101427527131121525043212532355867069203257229312
Number of bits of the biggest number in a constraint 450
Biggest sum of numbers in a constraint 5814709794364855124394590463104036274829130884415680534709393500410164485780207399841635394555886269312423583179230372744812869772975784
Number of bits of the biggest sum of numbers451
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 Integer values too big to handle...
0.01	c Parse Error 8
0.01	c Problem opening input file name: ROOT/tmp/node81/50417-1149921143/instance-50417-1149921143.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/node81/watcher-50417-1149921143 -o ROOT/results/node81/solver-50417-1149921143 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node81/50417-1149921143/instance-50417-1149921143.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.17 0.70 0.82 2/68 28962
/proc/meminfo: memFree=1472792/2055892 swapFree=4085344/4096564
[pid=28962] ppid=28960 vsize=4752 CPUtime=0
/proc/28962/stat : 28962 (bsolo) R 28960 28962 28916 0 -1 0 205 0 0 0 0 0 0 0 18 0 1 0 257753828 4866048 177 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 10538197 0 0 4096 16384 0 0 0 17 1 0 0
/proc/28962/statm: 1188 187 141 55 0 79 0

Child status: 0
Real time (s): 0.0205551
CPU time (s): 0.005998
CPU user time (s): 0.003999
CPU system time (s): 0.001999
CPU usage (%): 29.1802
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node81 on Sat Jun 10 06:32:24 UTC 2006


FILE ID= 50417-1149921143

PBS_JOBID= 386177

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=300-sizeP=151-sizeQ=300-692949159-max.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node81/50417-1149921143/instance-50417-1149921143.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node81/watcher-50417-1149921143 -o ROOT/results/node81/solver-50417-1149921143 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node81/50417-1149921143/instance-50417-1149921143.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  7e6b5d1bb2d5498810142d4e4cc2c6f4

RANDOM SEED= 595534095


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


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1473192 kB
Buffers:         41112 kB
Cached:         467840 kB
SwapCached:       2476 kB
Active:          80032 kB
Inactive:       437656 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1473192 kB
SwapTotal:     4096564 kB
SwapFree:      4085344 kB
Dirty:             120 kB
Writeback:           0 kB
Mapped:          16592 kB
Slab:            51596 kB
Committed_AS:   556824 kB
PageTables:       1288 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node81 on Sat Jun 10 06:32:24 UTC 2006