Trace number 50447

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.004998 0.0202691

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=240-sizeP=121-sizeQ=240-817963885.opb
MD5SUM4309132132f3075979f27880d2e9bd87
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 benchmark56.4524
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 variables29401
Total number of constraints87121
Number of constraints which are clauses87120
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 constraint29040
Number of terms in the objective function 121
Biggest coefficient in the objective function 1329227995784915872903807060280344576
Number of bits for the biggest coefficient in the objective function 121
Sum of the numbers in the objective function 2658455991569831745807614120560689151
Number of bits of the sum of numbers in the objective function 121
Biggest number in a constraint 1174271291386916613944740298394668513687841274454159935353645485766104512557304221731849499192384351515967488
Number of bits of the biggest number in a constraint 360
Biggest sum of numbers in a constraint 4697085165547666455778961193578674053925803487664042654232438232254482458885767017065112738772656890028524910
Number of bits of the biggest sum of numbers361
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/node67/50447-1149925020/instance-50447-1149925020.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/node67/watcher-50447-1149925020 -o ROOT/results/node67/solver-50447-1149925020 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node67/50447-1149925020/instance-50447-1149925020.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.54 0.85 0.95 2/64 20103
/proc/meminfo: memFree=1531576/2055920 swapFree=4181756/4192956
[pid=20103] ppid=20101 vsize=4664 CPUtime=0
/proc/20103/stat : 20103 (bsolo) R 20101 20103 20057 0 -1 0 155 0 0 0 0 0 0 0 19 0 1 0 258171483 4775936 135 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 6853885 0 0 4096 0 0 0 0 17 1 0 0
/proc/20103/statm: 1166 135 105 55 0 46 0

Child status: 0
Real time (s): 0.0202691
CPU time (s): 0.004998
CPU user time (s): 0.001999
CPU system time (s): 0.002999
CPU usage (%): 24.6582
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node67 on Sat Jun 10 07:37:01 UTC 2006


FILE ID= 50447-1149925020

PBS_JOBID= 386297

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=240-sizeP=121-sizeQ=240-817963885.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node67/50447-1149925020/instance-50447-1149925020.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node67/watcher-50447-1149925020 -o ROOT/results/node67/solver-50447-1149925020 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node67/50447-1149925020/instance-50447-1149925020.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  4309132132f3075979f27880d2e9bd87

RANDOM SEED= 525311326


/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.264
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	: 5931.00
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.264
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:       1531784 kB
Buffers:         42740 kB
Cached:         403796 kB
SwapCached:       2944 kB
Active:         122504 kB
Inactive:       332848 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1531784 kB
SwapTotal:     4192956 kB
SwapFree:      4181756 kB
Dirty:             268 kB
Writeback:           0 kB
Mapped:          14796 kB
Slab:            54688 kB
Committed_AS:   667716 kB
PageTables:       1472 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node67 on Sat Jun 10 07:37:01 UTC 2006