Trace number 50371

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

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=400-sizeP=201-sizeQ=400-87904490-max.opb
MD5SUMf145615704a2957501e412155c176c53
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 variables81001
Total number of constraints241201
Number of constraints which are clauses241200
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 constraint80400
Number of terms in the objective function 201
Biggest coefficient in the objective function 1606938044258990275541962092341162602522202993782792835301376
Number of bits for the biggest coefficient in the objective function 201
Sum of the numbers in the objective function 3213876088517980551083924184682325205044405987565585670602751
Number of bits of the sum of numbers in the objective function 201
Biggest number in a constraint 2074757784440496479256203931845580575506223116121218449997828664845326405706454073199853524473551897144098943305650394591197575537705887653943437417056981843530590901700754761842688
Number of bits of the biggest number in a constraint 600
Biggest sum of numbers in a constraint 8299031137761985917024815727382322302024892464484873799991313419664837827391154871651005228706296088699355875555839163484213727699346231811168069148386972247138995410784642717179115
Number of bits of the biggest sum of numbers601
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.06	c INFO: OSL Context initialized.
0.06	c Integer values too big to handle...
0.06	c Parse Error 8
0.06	c Problem opening input file name: ROOT/tmp/node64/50371-1149964064/instance-50371-1149964064.opb
0.06	s UNKNOWN
0.06	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/node64/watcher-50371-1149964064 -o ROOT/results/node64/solver-50371-1149964064 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node64/50371-1149964064/instance-50371-1149964064.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.13 0.03 0.08 2/64 11972
/proc/meminfo: memFree=1610104/2055920 swapFree=4192956/4192956
[pid=11972] ppid=11970 vsize=4932 CPUtime=0
/proc/11972/stat : 11972 (bsolo) D 11970 11972 11926 0 -1 0 370 0 0 0 0 0 0 0 18 0 1 0 9095271 5050368 331 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 2147483391 4096 16384 18446744072099781622 0 0 17 1 0 0
/proc/11972/statm: 1233 331 227 55 0 125 0

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

Launcher Data (download as text)

Begin job on node64 on Sat Jun 10 18:27:45 UTC 2006


FILE ID= 50371-1149964064

PBS_JOBID= 385993

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=400-sizeP=201-sizeQ=400-87904490-max.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node64/50371-1149964064/instance-50371-1149964064.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node64/watcher-50371-1149964064 -o ROOT/results/node64/solver-50371-1149964064 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node64/50371-1149964064/instance-50371-1149964064.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  f145615704a2957501e412155c176c53

RANDOM SEED= 490456028


/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.263
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.263
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:       1610312 kB
Buffers:         30120 kB
Cached:         359656 kB
SwapCached:          0 kB
Active:          81920 kB
Inactive:       322424 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1610312 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:             280 kB
Writeback:           0 kB
Mapped:          24920 kB
Slab:            27200 kB
Committed_AS:   123116 kB
PageTables:       1476 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node64 on Sat Jun 10 18:27:45 UTC 2006